Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6ef4dbf7f3d9b227ec59a41bb20770c5ea513eed47af62c20b52ea9602dbfbe

Tx prefix hash: 071cd7939db7ef1e3fa6c3422dd63cc1614876248d8fc84f8fa3c42873924fb3
Tx public key: e662a4f366b168088badc8d6693d7f0b3501ea761cec683af25396705f9b7bf5
Timestamp: 1713482003 Timestamp [UCT]: 2024-04-18 23:13:23 Age [y:d:h:m:s]: 00:351:01:20:49
Block: 1003511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250973 RingCT/type: yes/0
Extra: 01e662a4f366b168088badc8d6693d7f0b3501ea761cec683af25396705f9b7bf502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47032b88b7f4baefa10a5c2d8756deac2e9e9695ca7dcb7b3c4dcd2927afd687 0.600000000000 1464053 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": 1003521, "vin": [ { "gen": { "height": 1003511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47032b88b7f4baefa10a5c2d8756deac2e9e9695ca7dcb7b3c4dcd2927afd687" } } ], "extra": [ 1, 230, 98, 164, 243, 102, 177, 104, 8, 139, 173, 200, 214, 105, 61, 127, 11, 53, 1, 234, 118, 28, 236, 104, 58, 242, 83, 150, 112, 95, 155, 123, 245, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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