Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee6ccd0c1f8c958bfd111eb45f4e47043d2ee7598133efc3e8618baf25965019

Tx prefix hash: dd5cb5d3b175651f070834965df100a6df74d239146d6132e70e00a20857f34d
Tx public key: 1b597cb4a087802fedb2f8638419d297e59c4a75638ea4e1a28aa87c1d0c1f7f
Timestamp: 1649497755 Timestamp [UCT]: 2022-04-09 09:49:15 Age [y:d:h:m:s]: 02:235:20:45:32
Block: 476464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 688336 RingCT/type: yes/0
Extra: 011b597cb4a087802fedb2f8638419d297e59c4a75638ea4e1a28aa87c1d0c1f7f021100000001cb8520c2000000000000000000

1 output(s) for total of 16.191132184000 dcy

stealth address amount amount idx
00: 8a78751d305068fd8e54f722822d5df252b6db7d36321d7a3661ee7a280e7cc0 16.191132184000 896931 of 0

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": 476474, "vin": [ { "gen": { "height": 476464 } } ], "vout": [ { "amount": 16191132184, "target": { "key": "8a78751d305068fd8e54f722822d5df252b6db7d36321d7a3661ee7a280e7cc0" } } ], "extra": [ 1, 27, 89, 124, 180, 160, 135, 128, 47, 237, 178, 248, 99, 132, 25, 210, 151, 229, 156, 74, 117, 99, 142, 164, 225, 162, 138, 168, 124, 29, 12, 31, 127, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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