Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3b50294cd57b42d9ea902f6c628991cc39566d7630ce25d7623edd69504dc32

Tx prefix hash: b96b54c99cd4d8f44ce556db9b14e83192c52c976948755ecf56bdb4312f6822
Tx public key: f16236a210334b1e85450530d8a5461ebe39d4a06b466b07dcf72e1d8a70ae53
Timestamp: 1759754509 Timestamp [UCT]: 2025-10-06 12:41:49 Age [y:d:h:m:s]: 00:117:04:25:01
Block: 1384027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83723 RingCT/type: yes/0
Extra: 01f16236a210334b1e85450530d8a5461ebe39d4a06b466b07dcf72e1d8a70ae53021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca336777b35c711b4f6a9e29d5feb1bd9461a76dd3b4a8fd1b18555a7744a7ba 0.600000000000 1872176 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": 1384037, "vin": [ { "gen": { "height": 1384027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca336777b35c711b4f6a9e29d5feb1bd9461a76dd3b4a8fd1b18555a7744a7ba" } } ], "extra": [ 1, 241, 98, 54, 162, 16, 51, 75, 30, 133, 69, 5, 48, 216, 165, 70, 30, 190, 57, 212, 160, 107, 70, 107, 7, 220, 247, 46, 29, 138, 112, 174, 83, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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