Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68916a9ff8e0e636c27a4dc273138fd13acbd4c86383613e4f554464ff62b444

Tx prefix hash: c8fa70d1cc557d1fd58398932b028c16ea687a7b3a69f9c8ef246cb6190c44bb
Tx public key: e892a3edce58b0cb33d82c901348db88329399ae000a192d3137dc9be0766de9
Timestamp: 1709729664 Timestamp [UCT]: 2024-03-06 12:54:24 Age [y:d:h:m:s]: 00:251:22:53:48
Block: 972424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180370 RingCT/type: yes/0
Extra: 01e892a3edce58b0cb33d82c901348db88329399ae000a192d3137dc9be0766de90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7f9cb38560c97f33d65562d3c68cdfab03d307b99066dfa3c64a218a3fbfb20 0.600000000000 1432337 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": 972434, "vin": [ { "gen": { "height": 972424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7f9cb38560c97f33d65562d3c68cdfab03d307b99066dfa3c64a218a3fbfb20" } } ], "extra": [ 1, 232, 146, 163, 237, 206, 88, 176, 203, 51, 216, 44, 144, 19, 72, 219, 136, 50, 147, 153, 174, 0, 10, 25, 45, 49, 55, 220, 155, 224, 118, 109, 233, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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