Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00d342ec9e6cb9e3d898b058adb6bf1afab082a1ef8453bb241697599d9f6bd2

Tx prefix hash: 655b2900646ff2692011683408c5e27454aed0ca046979debaf02b2c558b36a1
Tx public key: 8d4ca02f482312c6cd578adb8d23ab74edc5fb0f714a9f6b72156f7ce584dfef
Timestamp: 1754814541 Timestamp [UCT]: 2025-08-10 08:29:01 Age [y:d:h:m:s]: 00:109:21:22:14
Block: 1344030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77739 RingCT/type: yes/0
Extra: 018d4ca02f482312c6cd578adb8d23ab74edc5fb0f714a9f6b72156f7ce584dfef02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d62bba4217d4316d958e2324db91fd68fe054d47d8facd0f7a901697e7f9cde8 0.600000000000 1831895 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": 1344040, "vin": [ { "gen": { "height": 1344030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d62bba4217d4316d958e2324db91fd68fe054d47d8facd0f7a901697e7f9cde8" } } ], "extra": [ 1, 141, 76, 160, 47, 72, 35, 18, 198, 205, 87, 138, 219, 141, 35, 171, 116, 237, 197, 251, 15, 113, 74, 159, 107, 114, 21, 111, 124, 229, 132, 223, 239, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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