Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ee5cfa3706784b5cc1c06d066b7ce3cf7d382c07865563e6164e239f0632928

Tx prefix hash: a00494de59b2be99d270e03b370808a693d2de0ccde305bb6fd75ec6b37a99e7
Tx public key: 7a5abb497bd741ccbfce8c55e8cb401736a01e973a6e2fc416b1ff76100cc158
Timestamp: 1737430241 Timestamp [UCT]: 2025-01-21 03:30:41 Age [y:d:h:m:s]: 00:148:14:59:47
Block: 1201867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105960 RingCT/type: yes/0
Extra: 017a5abb497bd741ccbfce8c55e8cb401736a01e973a6e2fc416b1ff76100cc1580211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c8afa92ec767c9f4e063136d50e2e11e029f1943680bf5be1f21a6f65f5e473 0.600000000000 1688524 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": 1201877, "vin": [ { "gen": { "height": 1201867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c8afa92ec767c9f4e063136d50e2e11e029f1943680bf5be1f21a6f65f5e473" } } ], "extra": [ 1, 122, 90, 187, 73, 123, 215, 65, 204, 191, 206, 140, 85, 232, 203, 64, 23, 54, 160, 30, 151, 58, 110, 47, 196, 22, 177, 255, 118, 16, 12, 193, 88, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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