Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9d72da0ffbf2c5965b8bb047abb266ccbe580792b6b12a8c4b8f233ccd16231

Tx prefix hash: 8dac3d3f1dcb619052f6eb3a2acc616ac51097743bd62f04d309366caaef608e
Tx public key: 6e3c20c8584e19e4b77fa1682276bcf765497359f9ea1b09c432b4c251c3798f
Timestamp: 1736270695 Timestamp [UCT]: 2025-01-07 17:24:55 Age [y:d:h:m:s]: 00:317:05:24:20
Block: 1192312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224231 RingCT/type: yes/0
Extra: 016e3c20c8584e19e4b77fa1682276bcf765497359f9ea1b09c432b4c251c3798f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a112c9a921eaaf1974921988a6224394af16a45fa8b5c753384c088bda37160 0.600000000000 1678861 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": 1192322, "vin": [ { "gen": { "height": 1192312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a112c9a921eaaf1974921988a6224394af16a45fa8b5c753384c088bda37160" } } ], "extra": [ 1, 110, 60, 32, 200, 88, 78, 25, 228, 183, 127, 161, 104, 34, 118, 188, 247, 101, 73, 115, 89, 249, 234, 27, 9, 196, 50, 180, 194, 81, 195, 121, 143, 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