Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b99cd5a3d564495caf20161dc676355294e0858670b64544f8ed3c7430cea45

Tx prefix hash: 891358f974954c4b1a573c02fe1d86b9b69a4b69d41923b2c9a1c9ec355120a3
Tx public key: 0d6c8312704f5fb0b9670f7590ca2c452f769ae968d27215c7aafe94022bc06e
Timestamp: 1716412882 Timestamp [UCT]: 2024-05-22 21:21:22 Age [y:d:h:m:s]: 00:246:09:25:50
Block: 1027814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176300 RingCT/type: yes/0
Extra: 010d6c8312704f5fb0b9670f7590ca2c452f769ae968d27215c7aafe94022bc06e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db2e53216646bc81a7ba74346ffe7638f50f33f9bd83de01420215c6229859ea 0.600000000000 1495639 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": 1027824, "vin": [ { "gen": { "height": 1027814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db2e53216646bc81a7ba74346ffe7638f50f33f9bd83de01420215c6229859ea" } } ], "extra": [ 1, 13, 108, 131, 18, 112, 79, 95, 176, 185, 103, 15, 117, 144, 202, 44, 69, 47, 118, 154, 233, 104, 210, 114, 21, 199, 170, 254, 148, 2, 43, 192, 110, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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