Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb7b1f5831abbef1e1cc453baa62f574b3ccf1e3ab6cee6f48c3abc3a4d8c2f7

Tx prefix hash: 2a12c76ec2cc93a963b72db5f99f48217aecd40aa3b31dd3809124fd145990c1
Tx public key: cd72a2eaf1f85c0e111d498051adae4f1304f31458ff59a1ea89e9cc1c7d4298
Timestamp: 1703626918 Timestamp [UCT]: 2023-12-26 21:41:58 Age [y:d:h:m:s]: 01:118:08:05:29
Block: 921816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345691 RingCT/type: yes/0
Extra: 01cd72a2eaf1f85c0e111d498051adae4f1304f31458ff59a1ea89e9cc1c7d429802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0aa47ba2af881091f5d39e1d1ca94e8a23871d34fba589e57d0dd23880b7fbb1 0.600000000000 1379510 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": 921826, "vin": [ { "gen": { "height": 921816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aa47ba2af881091f5d39e1d1ca94e8a23871d34fba589e57d0dd23880b7fbb1" } } ], "extra": [ 1, 205, 114, 162, 234, 241, 248, 92, 14, 17, 29, 73, 128, 81, 173, 174, 79, 19, 4, 243, 20, 88, 255, 89, 161, 234, 137, 233, 204, 28, 125, 66, 152, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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