Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99c722c626e6d64edf384aaad9c71d8dbf895c4ca006ed84d31c3acf9c143d1d

Tx prefix hash: 4fedd4d29aa7a8c29086390b16db9c65601436ca249981a47caba3fc9154133e
Tx public key: 29f8f17d7ccf4046cf5a27b8d4217ebe8be5d75e02df179b0a48ab9c257b87f7
Timestamp: 1756381458 Timestamp [UCT]: 2025-08-28 11:44:18 Age [y:d:h:m:s]: 00:135:08:13:41
Block: 1356251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96740 RingCT/type: yes/0
Extra: 0129f8f17d7ccf4046cf5a27b8d4217ebe8be5d75e02df179b0a48ab9c257b87f70211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2885e13be7b3838afc21c3c83667006e55dded8e59f51810d3026a41f6a4144e 0.600000000000 1844258 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": 1356261, "vin": [ { "gen": { "height": 1356251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2885e13be7b3838afc21c3c83667006e55dded8e59f51810d3026a41f6a4144e" } } ], "extra": [ 1, 41, 248, 241, 125, 124, 207, 64, 70, 207, 90, 39, 184, 212, 33, 126, 190, 139, 229, 215, 94, 2, 223, 23, 155, 10, 72, 171, 156, 37, 123, 135, 247, 2, 17, 0, 0, 0, 3, 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