Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84f54fa938953f4f55d9e364bf4fed54a94ebc14c620db6ffd121f7e4efe17ca

Tx prefix hash: 8c661386a94e8054754116571d0acf38b95f4f3f0bc633e11e3461f9968849a9
Tx public key: e2658b8a3d8e29daa27084dc7ce14acd01d4b1c4e502d41c75557e151a626023
Timestamp: 1706589543 Timestamp [UCT]: 2024-01-30 04:39:03 Age [y:d:h:m:s]: 01:311:10:16:30
Block: 946354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481406 RingCT/type: yes/0
Extra: 01e2658b8a3d8e29daa27084dc7ce14acd01d4b1c4e502d41c75557e151a6260230211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3922e71529b3aecdb34c39777f4384404586d7da19a96302f8d05ca2eaca868b 0.600000000000 1404686 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": 946364, "vin": [ { "gen": { "height": 946354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3922e71529b3aecdb34c39777f4384404586d7da19a96302f8d05ca2eaca868b" } } ], "extra": [ 1, 226, 101, 139, 138, 61, 142, 41, 218, 162, 112, 132, 220, 124, 225, 74, 205, 1, 212, 177, 196, 229, 2, 212, 28, 117, 85, 126, 21, 26, 98, 96, 35, 2, 17, 0, 0, 0, 2, 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