Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 683824a1788d6a96fb2675bc2725c7ef8ae8d8d3fb421720aecf352897ffe8a2

Tx prefix hash: 2e5924db662a6fe9a73dedf6c684d3bfffdd4d4b96bf801f68b3ea074b702d34
Tx public key: a9f79a7168724c18409192883b1b79753ca4c6287d37be7801bab640671e4823
Timestamp: 1743999212 Timestamp [UCT]: 2025-04-07 04:13:32 Age [y:d:h:m:s]: 00:295:19:52:28
Block: 1256009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209081 RingCT/type: yes/0
Extra: 01a9f79a7168724c18409192883b1b79753ca4c6287d37be7801bab640671e4823021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa9fb719814269bf86b63f13729c44656a6bbba75addf27c5dfb10e44aae10b7 0.600000000000 1743118 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": 1256019, "vin": [ { "gen": { "height": 1256009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa9fb719814269bf86b63f13729c44656a6bbba75addf27c5dfb10e44aae10b7" } } ], "extra": [ 1, 169, 247, 154, 113, 104, 114, 76, 24, 64, 145, 146, 136, 59, 27, 121, 117, 60, 164, 198, 40, 125, 55, 190, 120, 1, 186, 182, 64, 103, 30, 72, 35, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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