Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3be43ee505e66b4432610dd1f0fdcc4005554d236d1316d26cf194d9b59b3b2e

Tx prefix hash: 4954f02aa577c874142d38a72f8ed7a06a0c8e18b9438827fd10c80f93225c3a
Tx public key: bd9fdbcccab96d8ff2b7932b49b267cf4ebee2ad1e20916e2a8388e6dba171d9
Timestamp: 1761142751 Timestamp [UCT]: 2025-10-22 14:19:11 Age [y:d:h:m:s]: 00:019:10:14:18
Block: 1395545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13900 RingCT/type: yes/0
Extra: 01bd9fdbcccab96d8ff2b7932b49b267cf4ebee2ad1e20916e2a8388e6dba171d902110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 230dcdfb588da0be533482d6b5c72a30bca0df011e5bc78992053fedc81fb406 0.600000000000 1883824 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": 1395555, "vin": [ { "gen": { "height": 1395545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "230dcdfb588da0be533482d6b5c72a30bca0df011e5bc78992053fedc81fb406" } } ], "extra": [ 1, 189, 159, 219, 204, 202, 185, 109, 143, 242, 183, 147, 43, 73, 178, 103, 207, 78, 190, 226, 173, 30, 32, 145, 110, 42, 131, 136, 230, 219, 161, 113, 217, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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