Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e57f079626e170a7414a9ea26fa9d4914955e72f34d56b808faa95617a7d4182

Tx prefix hash: b3823b95785adf5ed1aa19c531339ad5c8867e0fe3d3e13e6cb1fff3353226e6
Tx public key: 0f8a8b8038d9afeb45a31137dc6823750dae95d25ff0a6f6c79e171bb5761ffd
Timestamp: 1733589044 Timestamp [UCT]: 2024-12-07 16:30:44 Age [y:d:h:m:s]: 00:106:02:45:19
Block: 1170113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75628 RingCT/type: yes/0
Extra: 010f8a8b8038d9afeb45a31137dc6823750dae95d25ff0a6f6c79e171bb5761ffd021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cadf0281555df552359cf4f949ab798eebcfecf8579d46c2c3248c8e9e45f5f4 0.600000000000 1655842 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": 1170123, "vin": [ { "gen": { "height": 1170113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cadf0281555df552359cf4f949ab798eebcfecf8579d46c2c3248c8e9e45f5f4" } } ], "extra": [ 1, 15, 138, 139, 128, 56, 217, 175, 235, 69, 163, 17, 55, 220, 104, 35, 117, 13, 174, 149, 210, 95, 240, 166, 246, 199, 158, 23, 27, 181, 118, 31, 253, 2, 17, 0, 0, 0, 4, 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