Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf3e1b62ee4ff0baa8877a58f157cb3e3b5cf050457b0b9236b5fd96c7ad1a04

Tx prefix hash: e03e810233489868d02cd70a1f239e72cbbac61ba87d4672d55f78e59a971eee
Tx public key: 0ccb0b6446cc6039ec72d87facc0736cbab5a33d1c8157dfaea60f079faf0709
Timestamp: 1713051963 Timestamp [UCT]: 2024-04-13 23:46:03 Age [y:d:h:m:s]: 01:206:03:46:15
Block: 999929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406005 RingCT/type: yes/0
Extra: 010ccb0b6446cc6039ec72d87facc0736cbab5a33d1c8157dfaea60f079faf070902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5691b92245d3852f299860df5cc0354c8423ae74f6c3fa8b47a73f4141a0fdb 0.600000000000 1460417 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": 999939, "vin": [ { "gen": { "height": 999929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5691b92245d3852f299860df5cc0354c8423ae74f6c3fa8b47a73f4141a0fdb" } } ], "extra": [ 1, 12, 203, 11, 100, 70, 204, 96, 57, 236, 114, 216, 127, 172, 192, 115, 108, 186, 181, 163, 61, 28, 129, 87, 223, 174, 166, 15, 7, 159, 175, 7, 9, 2, 17, 0, 0, 0, 5, 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