Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 966f57148a82875fd8a555805754650b9e1aae7596b0167b1dbf19d47b28f356

Tx prefix hash: ed54bf3e503d0c85e1d908d77f9b36b47692cbf63115b861c07834fc2cea4677
Tx public key: b6cce0c14c2e4f6cc09b9f74a81b6eb52de78e3d2c10eb86bdcecfb74714bf4a
Timestamp: 1726675839 Timestamp [UCT]: 2024-09-18 16:10:39 Age [y:d:h:m:s]: 01:049:17:59:19
Block: 1112901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293961 RingCT/type: yes/0
Extra: 01b6cce0c14c2e4f6cc09b9f74a81b6eb52de78e3d2c10eb86bdcecfb74714bf4a021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 856670626ceca3603706a8b991e6859c897077f876ed4906bb5a9dce228a9422 0.600000000000 1592384 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": 1112911, "vin": [ { "gen": { "height": 1112901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "856670626ceca3603706a8b991e6859c897077f876ed4906bb5a9dce228a9422" } } ], "extra": [ 1, 182, 204, 224, 193, 76, 46, 79, 108, 192, 155, 159, 116, 168, 27, 110, 181, 45, 231, 142, 61, 44, 16, 235, 134, 189, 206, 207, 183, 71, 20, 191, 74, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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