Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7033e135a3acb89256f2b43127b0122823f83f93a01e05f474a583caa547a58d

Tx prefix hash: 0b33454da6f88254bb3f8c00da921f1eb4fac50dabff47cb99112fe8ff24ec2e
Tx public key: 6f64ec1d2ef7d87c9e5507e49d7b299ee870d1c06c98d3fca258b984ac1815ce
Timestamp: 1734061038 Timestamp [UCT]: 2024-12-13 03:37:18 Age [y:d:h:m:s]: 00:102:09:04:15
Block: 1174038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72939 RingCT/type: yes/0
Extra: 016f64ec1d2ef7d87c9e5507e49d7b299ee870d1c06c98d3fca258b984ac1815ce021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4437bd393371dc178dcc26954671ae037206a81a5bd956c5d968041780a31c4f 0.600000000000 1660139 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": 1174048, "vin": [ { "gen": { "height": 1174038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4437bd393371dc178dcc26954671ae037206a81a5bd956c5d968041780a31c4f" } } ], "extra": [ 1, 111, 100, 236, 29, 46, 247, 216, 124, 158, 85, 7, 228, 157, 123, 41, 158, 232, 112, 209, 192, 108, 152, 211, 252, 162, 88, 185, 132, 172, 24, 21, 206, 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