Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2454ed43ab4d18e567e8d459c9f330a6fa6619e5a5708f098f3504b4c2bf4638

Tx prefix hash: 9816a05ed473b03486aee91de1b33c3479d3c7bfb32d2741da1877afaa8a0b46
Tx public key: df9ef287d5b4062bdd4c902ef9b23762e6a77d099f8483035cf2cc0c3791862d
Timestamp: 1732993106 Timestamp [UCT]: 2024-11-30 18:58:26 Age [y:d:h:m:s]: 00:114:00:03:28
Block: 1165178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81267 RingCT/type: yes/0
Extra: 01df9ef287d5b4062bdd4c902ef9b23762e6a77d099f8483035cf2cc0c3791862d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67098a54326d33beac19817a658a5f83b9b4716360a4417aec562d5ab7d52805 0.600000000000 1650853 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": 1165188, "vin": [ { "gen": { "height": 1165178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67098a54326d33beac19817a658a5f83b9b4716360a4417aec562d5ab7d52805" } } ], "extra": [ 1, 223, 158, 242, 135, 213, 180, 6, 43, 221, 76, 144, 46, 249, 178, 55, 98, 230, 167, 125, 9, 159, 132, 131, 3, 92, 242, 204, 12, 55, 145, 134, 45, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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