Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9df54199f4c44d125765572fe029de044a6b7736ddf4b0b26bc6f3403f916025

Tx prefix hash: 464ee34db6c7e3f28ec945c89d817c309bfa4813d3c4b46753ecccfc1fc67296
Tx public key: 282258c73852e019d21d5cea5b0a71a6105e1a91f3745b849ecb9afb10d3ae51
Timestamp: 1744290211 Timestamp [UCT]: 2025-04-10 13:03:31 Age [y:d:h:m:s]: 00:222:13:52:32
Block: 1258434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156803 RingCT/type: yes/0
Extra: 01282258c73852e019d21d5cea5b0a71a6105e1a91f3745b849ecb9afb10d3ae510211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6856546f6ee74ab2cb92676e36e5686dd2d9d10fdf56b9107eb87f461960303 0.600000000000 1745567 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": 1258444, "vin": [ { "gen": { "height": 1258434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6856546f6ee74ab2cb92676e36e5686dd2d9d10fdf56b9107eb87f461960303" } } ], "extra": [ 1, 40, 34, 88, 199, 56, 82, 224, 25, 210, 29, 92, 234, 91, 10, 113, 166, 16, 94, 26, 145, 243, 116, 91, 132, 158, 203, 154, 251, 16, 211, 174, 81, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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