Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c934cd52b15c740c51bb578760935b733576d231ce9e5bb34825183cd93b4b6e

Tx prefix hash: e9b70dfba7513046015f2cc6fe81cc052dba8b3c2e8c876190d3d7dbb7d6810f
Tx public key: ca345e830b963352a7d73c8c8b625f5b893f41bd0271e24cebadecb8ba27c69a
Timestamp: 1736381499 Timestamp [UCT]: 2025-01-09 00:11:39 Age [y:d:h:m:s]: 00:077:14:02:35
Block: 1193230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55211 RingCT/type: yes/0
Extra: 01ca345e830b963352a7d73c8c8b625f5b893f41bd0271e24cebadecb8ba27c69a021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6a54726bcd9192246710aeeed55982ad93627033e653292c948f9f5e0d2720f 0.600000000000 1679789 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1193240, "vin": [ { "gen": { "height": 1193230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6a54726bcd9192246710aeeed55982ad93627033e653292c948f9f5e0d2720f" } } ], "extra": [ 1, 202, 52, 94, 131, 11, 150, 51, 82, 167, 215, 60, 140, 139, 98, 95, 91, 137, 63, 65, 189, 2, 113, 226, 76, 235, 173, 236, 184, 186, 39, 198, 154, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8