Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73e683ed8bd70f12118b745cc46e875f85c078cbe8ff01476ec0bcb022ad28e8

Tx prefix hash: c7cbe69b0012eb85e7897644e74908aa163210df20e6453c4fc18f251b08d5b5
Tx public key: 871e4fba810e68d680de3a1a9298f2a28acb3eca75c424964f68af858448ebcd
Timestamp: 1698358881 Timestamp [UCT]: 2023-10-26 22:21:21 Age [y:d:h:m:s]: 01:089:04:15:29
Block: 878355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324913 RingCT/type: yes/0
Extra: 01871e4fba810e68d680de3a1a9298f2a28acb3eca75c424964f68af858448ebcd021100000001faf35c9c000000000000000000

1 output(s) for total of 0.754475736000 dcy

stealth address amount amount idx
00: e038098f66de9c0224e73018f464a223df6cbd7bd6e37b5ad1c3af25f26f1fc4 0.754475736000 1333793 of 0

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": 878365, "vin": [ { "gen": { "height": 878355 } } ], "vout": [ { "amount": 754475736, "target": { "key": "e038098f66de9c0224e73018f464a223df6cbd7bd6e37b5ad1c3af25f26f1fc4" } } ], "extra": [ 1, 135, 30, 79, 186, 129, 14, 104, 214, 128, 222, 58, 26, 146, 152, 242, 162, 138, 203, 62, 202, 117, 196, 36, 150, 79, 104, 175, 133, 132, 72, 235, 205, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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