Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dff65a17052e6adfb9c8d60f381a71b4a3d5112da5d46955d26ef9660660395e

Tx prefix hash: 7bf09fbee21337935de6a89d49fedf8afe082ae95fb460d8f87b5626a31d19c0
Tx public key: 1c7220f2f93447d92aa62dd17cce8d6a835ac1295944e4d023e23e1982be9ed5
Timestamp: 1709031479 Timestamp [UCT]: 2024-02-27 10:57:59 Age [y:d:h:m:s]: 01:337:06:08:25
Block: 966627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499693 RingCT/type: yes/0
Extra: 011c7220f2f93447d92aa62dd17cce8d6a835ac1295944e4d023e23e1982be9ed50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 047024fd41096983d618bd9f3501ad7c17b20e3dbdcfefd2ebd20183efe12db0 0.600000000000 1426394 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": 966637, "vin": [ { "gen": { "height": 966627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "047024fd41096983d618bd9f3501ad7c17b20e3dbdcfefd2ebd20183efe12db0" } } ], "extra": [ 1, 28, 114, 32, 242, 249, 52, 71, 217, 42, 166, 45, 209, 124, 206, 141, 106, 131, 90, 193, 41, 89, 68, 228, 208, 35, 226, 62, 25, 130, 190, 158, 213, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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