Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4ea2e097254abbfaceda13e874eb9f0e296b6db0a808a2644a68679374c6bff

Tx prefix hash: 765d33140e594c2423183def0be4ba745e5e720503de3c81e3477f5945ff196f
Tx public key: 30f8ecfa0740ab3be294a0c84ba654f67ba2d84f6f9f1c23a4ecf78717b964f4
Timestamp: 1734019816 Timestamp [UCT]: 2024-12-12 16:10:16 Age [y:d:h:m:s]: 00:187:10:12:43
Block: 1173697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133658 RingCT/type: yes/0
Extra: 0130f8ecfa0740ab3be294a0c84ba654f67ba2d84f6f9f1c23a4ecf78717b964f4021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 992ad131126cb624534c39842128a34cbe8ce940cd042c814a08b43a4d18ce24 0.600000000000 1659748 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": 1173707, "vin": [ { "gen": { "height": 1173697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "992ad131126cb624534c39842128a34cbe8ce940cd042c814a08b43a4d18ce24" } } ], "extra": [ 1, 48, 248, 236, 250, 7, 64, 171, 59, 226, 148, 160, 200, 75, 166, 84, 246, 123, 162, 216, 79, 111, 159, 28, 35, 164, 236, 247, 135, 23, 185, 100, 244, 2, 17, 0, 0, 0, 6, 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