Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a423b7ed3776572e86d4cfa7fed7dfc93c71bbeb7a06c28852f97c3ef6cccd

Tx prefix hash: cb27169c40d9f90238ef303ac2a9aa4b63f16cc1af18b77f893dc4d7b63bf1f8
Tx public key: d6eae52df5d33d9a1b723993e1d4843ff216b177820017cf91ded73b68312ccd
Timestamp: 1705687141 Timestamp [UCT]: 2024-01-19 17:59:01 Age [y:d:h:m:s]: 01:083:12:32:11
Block: 938866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320801 RingCT/type: yes/0
Extra: 01d6eae52df5d33d9a1b723993e1d4843ff216b177820017cf91ded73b68312ccd0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8faefee070fa3c6a377b50d45edab376ba310741b07e84c8bb908b433ade0751 0.600000000000 1396948 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": 938876, "vin": [ { "gen": { "height": 938866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8faefee070fa3c6a377b50d45edab376ba310741b07e84c8bb908b433ade0751" } } ], "extra": [ 1, 214, 234, 229, 45, 245, 211, 61, 154, 27, 114, 57, 147, 225, 212, 132, 63, 242, 22, 177, 119, 130, 0, 23, 207, 145, 222, 215, 59, 104, 49, 44, 205, 2, 17, 0, 0, 0, 3, 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