Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbad24ba0cddb3835f547af87596c4ae64aae7a8444ecf6a1cdf3b2b82b84e03

Tx prefix hash: f1ef0b4b05a052061acccab3736c0485d2fd0a4db6264376292ddf656c76e378
Tx public key: 1ef16e9c373fa1c79799d77ce93de5ccb202dff788d50a8bfe3b10ad432d34a9
Timestamp: 1707496384 Timestamp [UCT]: 2024-02-09 16:33:04 Age [y:d:h:m:s]: 01:051:03:54:46
Block: 953882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297621 RingCT/type: yes/0
Extra: 011ef16e9c373fa1c79799d77ce93de5ccb202dff788d50a8bfe3b10ad432d34a902110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdf144dd95ac858d009ae8a35013000ef90af11c2602226d57c66a237a63d75b 0.600000000000 1413152 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": 953892, "vin": [ { "gen": { "height": 953882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdf144dd95ac858d009ae8a35013000ef90af11c2602226d57c66a237a63d75b" } } ], "extra": [ 1, 30, 241, 110, 156, 55, 63, 161, 199, 151, 153, 215, 124, 233, 61, 229, 204, 178, 2, 223, 247, 136, 213, 10, 139, 254, 59, 16, 173, 67, 45, 52, 169, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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