Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aa74eff95ca35f746cc622d4e305e2183a7685df836c3aebd8120611ed6ac70

Tx prefix hash: b5e5eef38b49ee3e767f953c852bc64fec68434f7798966981bb012f7b7a01ed
Tx public key: 7aebc878ceb5e982392d0c42a043528b59c13a326e1a517d38186b3cfd6a2c16
Timestamp: 1738456338 Timestamp [UCT]: 2025-02-02 00:32:18 Age [y:d:h:m:s]: 00:249:03:11:38
Block: 1210134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175771 RingCT/type: yes/0
Extra: 017aebc878ceb5e982392d0c42a043528b59c13a326e1a517d38186b3cfd6a2c160211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3538832c620e1fac9033b20a7c512e908d0d2c221c1be84c95672884190bbd31 0.600000000000 1696885 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": 1210144, "vin": [ { "gen": { "height": 1210134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3538832c620e1fac9033b20a7c512e908d0d2c221c1be84c95672884190bbd31" } } ], "extra": [ 1, 122, 235, 200, 120, 206, 181, 233, 130, 57, 45, 12, 66, 160, 67, 82, 139, 89, 193, 58, 50, 110, 26, 81, 125, 56, 24, 107, 60, 253, 106, 44, 22, 2, 17, 0, 0, 0, 1, 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