Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cf35a7aa950c79f60bf08c16bd47265887bbc1d7ece79bb3c791a1a7cbe6070

Tx prefix hash: 8b58b9de4dfcdec609020353684cd63dcd7e878fbdc51cd7638a0a56eeae7417
Tx public key: 3ae048c6703274ddcf04dfcd1ae03073e350b7f209fcb9abfff7e8a448634bf5
Timestamp: 1581818840 Timestamp [UCT]: 2020-02-16 02:07:20 Age [y:d:h:m:s]: 05:018:02:29:44
Block: 65652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1166060 RingCT/type: yes/0
Extra: 013ae048c6703274ddcf04dfcd1ae03073e350b7f209fcb9abfff7e8a448634bf502110000000212c4732d000000000000000000

1 output(s) for total of 371.936226508000 dcy

stealth address amount amount idx
00: df2256770d13e3f2a0e4588039b749089d56f392bc5bd23b9b25abe925c2c68f 371.936226508000 121178 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": 65662, "vin": [ { "gen": { "height": 65652 } } ], "vout": [ { "amount": 371936226508, "target": { "key": "df2256770d13e3f2a0e4588039b749089d56f392bc5bd23b9b25abe925c2c68f" } } ], "extra": [ 1, 58, 224, 72, 198, 112, 50, 116, 221, 207, 4, 223, 205, 26, 224, 48, 115, 227, 80, 183, 242, 9, 252, 185, 171, 255, 247, 232, 164, 72, 99, 75, 245, 2, 17, 0, 0, 0, 2, 18, 196, 115, 45, 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