Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3afe3fe55ab898fb05bc7502e81e202e2089fb8e8e6d3b438c2f57da5e8f9b56

Tx prefix hash: 8d6ccf91841819fc3ecc1681508bd83dddaa249354c4244a48f6f7fe28331f56
Tx public key: 59784df8b3b19fae0678c2448c969b8d9a1379d9c4cac2f3eff06c01ec357dce
Timestamp: 1734969878 Timestamp [UCT]: 2024-12-23 16:04:38 Age [y:d:h:m:s]: 00:105:19:58:26
Block: 1181577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75384 RingCT/type: yes/0
Extra: 0159784df8b3b19fae0678c2448c969b8d9a1379d9c4cac2f3eff06c01ec357dce0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8106be3afa10b314927fc46e46456d5e3654d7e29ee5b83f30bc47aaa80c2be 0.600000000000 1668002 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": 1181587, "vin": [ { "gen": { "height": 1181577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8106be3afa10b314927fc46e46456d5e3654d7e29ee5b83f30bc47aaa80c2be" } } ], "extra": [ 1, 89, 120, 77, 248, 179, 177, 159, 174, 6, 120, 194, 68, 140, 150, 155, 141, 154, 19, 121, 217, 196, 202, 194, 243, 239, 240, 108, 1, 236, 53, 125, 206, 2, 17, 0, 0, 0, 4, 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