Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe51220bbc74715d935faa90a4eab036f30dc0141502d4418d1200a60ee5fba5

Tx prefix hash: 71da2db3c8094cea181d0731b134176279c4e5cb0f8e2bfadeb22eac2ad40d7a
Tx public key: 8c8ce5afa2672f91ca1e8dfe08aaf6dfb12bdcb80324c87bdfb1960774e093c7
Timestamp: 1728639159 Timestamp [UCT]: 2024-10-11 09:32:39 Age [y:d:h:m:s]: 01:038:21:17:16
Block: 1129183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286169 RingCT/type: yes/0
Extra: 018c8ce5afa2672f91ca1e8dfe08aaf6dfb12bdcb80324c87bdfb1960774e093c702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76976cc9f43d73aa2e9c1efd6ae9c0986eb83b2df37fa6aef6b40889a34ecfcb 0.600000000000 1612008 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": 1129193, "vin": [ { "gen": { "height": 1129183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76976cc9f43d73aa2e9c1efd6ae9c0986eb83b2df37fa6aef6b40889a34ecfcb" } } ], "extra": [ 1, 140, 140, 229, 175, 162, 103, 47, 145, 202, 30, 141, 254, 8, 170, 246, 223, 177, 43, 220, 184, 3, 36, 200, 123, 223, 177, 150, 7, 116, 224, 147, 199, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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