Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e4a82e682537ca743b84c99a81acffc0e911d8e67e1deb8d16092ce3007b69f

Tx prefix hash: 065c9761fed9b87b192d8bc5269d317b0cc1d7caa166ccd0e004e31c9921fcd4
Tx public key: bac608ab0c041d98688c9f80c5e1bd15f3b867b774d36d72b5d6548f40be117a
Timestamp: 1763397791 Timestamp [UCT]: 2025-11-17 16:43:11 Age [y:d:h:m:s]: 00:074:04:07:11
Block: 1414212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52933 RingCT/type: yes/0
Extra: 01bac608ab0c041d98688c9f80c5e1bd15f3b867b774d36d72b5d6548f40be117a02110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb2f5adc1a323c536bc988e25e7e7541134d2d284e36e4ffb91484620b19d483 0.600000000000 1902699 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": 1414222, "vin": [ { "gen": { "height": 1414212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb2f5adc1a323c536bc988e25e7e7541134d2d284e36e4ffb91484620b19d483" } } ], "extra": [ 1, 186, 198, 8, 171, 12, 4, 29, 152, 104, 140, 159, 128, 197, 225, 189, 21, 243, 184, 103, 183, 116, 211, 109, 114, 181, 214, 84, 143, 64, 190, 17, 122, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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