Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f163247dbcf220b2216ec2705184c0871306b93ce63fefd5e87c5ea6e7844b06

Tx prefix hash: f6ecba2ed8acacbf6c596d37c0a5a08ed85484be9d4fc68c9197f8e24b637b4a
Tx public key: 734fb062baf8f7c75c375b9de446adcd954a415ab2480a6e4aa2ed0c82e51c96
Timestamp: 1732811465 Timestamp [UCT]: 2024-11-28 16:31:05 Age [y:d:h:m:s]: 00:131:07:05:57
Block: 1163673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93635 RingCT/type: yes/0
Extra: 01734fb062baf8f7c75c375b9de446adcd954a415ab2480a6e4aa2ed0c82e51c960211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82134b163b9f8ddacd48f428b840660fa476c8d6bac6690e96251d961aaed287 0.600000000000 1649340 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": 1163683, "vin": [ { "gen": { "height": 1163673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82134b163b9f8ddacd48f428b840660fa476c8d6bac6690e96251d961aaed287" } } ], "extra": [ 1, 115, 79, 176, 98, 186, 248, 247, 199, 92, 55, 91, 157, 228, 70, 173, 205, 149, 74, 65, 90, 178, 72, 10, 110, 74, 162, 237, 12, 130, 229, 28, 150, 2, 17, 0, 0, 0, 3, 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