Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8453e94a37563008dae2b7a10da6f8e699aec73510354359a5940d87293dfa29

Tx prefix hash: e2bca9cad49b512ba21338c02897d3f47d1d1499ed1b95e2063d3dbd43eefd79
Tx public key: a5027e86f0268500c77a3ce7ab19e8a9fec9400cf590b01ef44b804c3a94052e
Timestamp: 1733795290 Timestamp [UCT]: 2024-12-10 01:48:10 Age [y:d:h:m:s]: 00:103:07:00:44
Block: 1171830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73605 RingCT/type: yes/0
Extra: 01a5027e86f0268500c77a3ce7ab19e8a9fec9400cf590b01ef44b804c3a94052e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ad3c74f35ef2f63b0632d6f91255184e9e3471c9ae80b08f955a262eb2a209c 0.600000000000 1657639 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": 1171840, "vin": [ { "gen": { "height": 1171830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ad3c74f35ef2f63b0632d6f91255184e9e3471c9ae80b08f955a262eb2a209c" } } ], "extra": [ 1, 165, 2, 126, 134, 240, 38, 133, 0, 199, 122, 60, 231, 171, 25, 232, 169, 254, 201, 64, 12, 245, 144, 176, 30, 244, 75, 128, 76, 58, 148, 5, 46, 2, 17, 0, 0, 0, 1, 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