Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8855725991c6c36dcf5c04c3a9fc71f774d00fbb57b375e66f60ce4915b023c

Tx prefix hash: b12688f9df7ce69d10e3856c082c95ea9ffbd3efb4d51e9e78ac8932d15a7e03
Tx public key: 38b1e127fa2d680533618501dcfc57f35e51f50813bfb62f52ce87f769ade9b2
Timestamp: 1734156557 Timestamp [UCT]: 2024-12-14 06:09:17 Age [y:d:h:m:s]: 00:107:08:30:03
Block: 1174828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76494 RingCT/type: yes/0
Extra: 0138b1e127fa2d680533618501dcfc57f35e51f50813bfb62f52ce87f769ade9b20211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baf4d555022e726d0828240830d4b581d1c09002acab073ad2c872a50d24f7d1 0.600000000000 1661029 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": 1174838, "vin": [ { "gen": { "height": 1174828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baf4d555022e726d0828240830d4b581d1c09002acab073ad2c872a50d24f7d1" } } ], "extra": [ 1, 56, 177, 225, 39, 250, 45, 104, 5, 51, 97, 133, 1, 220, 252, 87, 243, 94, 81, 245, 8, 19, 191, 182, 47, 82, 206, 135, 247, 105, 173, 233, 178, 2, 17, 0, 0, 0, 6, 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