Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cda03b472f651499a10dded64f6602fcf54533ed3e6d27c24c37f781a5e4fecd

Tx prefix hash: 729f3f359fe9efaa57f4fa75f7bef6072f37e54dd1937998d9df9b70f0b062c5
Tx public key: fd63495de3a9bf8a76b8949ef3dcbc94712090a0544f0582d8e9a92dbc9b5105
Timestamp: 1722732686 Timestamp [UCT]: 2024-08-04 00:51:26 Age [y:d:h:m:s]: 00:112:20:33:25
Block: 1080212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80738 RingCT/type: yes/0
Extra: 01fd63495de3a9bf8a76b8949ef3dcbc94712090a0544f0582d8e9a92dbc9b510502110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4681ffb0fac9f045662646e1c2d9df58a083183f98374093d92608ad8409028c 0.600000000000 1553485 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": 1080222, "vin": [ { "gen": { "height": 1080212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4681ffb0fac9f045662646e1c2d9df58a083183f98374093d92608ad8409028c" } } ], "extra": [ 1, 253, 99, 73, 93, 227, 169, 191, 138, 118, 184, 148, 158, 243, 220, 188, 148, 113, 32, 144, 160, 84, 79, 5, 130, 216, 233, 169, 45, 188, 155, 81, 5, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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