Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a8d22cc6637348dfe13e45a13fe1c1877dffd03eb3f802d26a35919a1a27145

Tx prefix hash: d449a61f0153ae45295d12bf8cbd9661dc4c9ec18cf42be4e23044c0d2109704
Tx public key: bb396f2dcbe6cd6aa884086c2dde165e2f4f83a7c5d052dca497f25bea21e335
Timestamp: 1738333850 Timestamp [UCT]: 2025-01-31 14:30:50 Age [y:d:h:m:s]: 00:294:05:47:47
Block: 1209129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208058 RingCT/type: yes/0
Extra: 01bb396f2dcbe6cd6aa884086c2dde165e2f4f83a7c5d052dca497f25bea21e335021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e10e938268c5c4c71deaffc296e22961914467e0b42a72b3e847028eed55d86 0.600000000000 1695870 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": 1209139, "vin": [ { "gen": { "height": 1209129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e10e938268c5c4c71deaffc296e22961914467e0b42a72b3e847028eed55d86" } } ], "extra": [ 1, 187, 57, 111, 45, 203, 230, 205, 106, 168, 132, 8, 108, 45, 222, 22, 94, 47, 79, 131, 167, 197, 208, 82, 220, 164, 151, 242, 91, 234, 33, 227, 53, 2, 17, 0, 0, 0, 3, 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