Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03e01c9bf71c297a813865fc10b94471d9b78e987df9f1d8b8428ad8848510a1

Tx prefix hash: 1ab493509f22da29cfce54a877f90ee2ee5eff479a2fc570f300b8b2022e51bd
Tx public key: 257e0cb44744ee7a37171df19f2cc0d8bc2a7c96f298fe1bdbc88e227684d40d
Timestamp: 1761792662 Timestamp [UCT]: 2025-10-30 02:51:02 Age [y:d:h:m:s]: 00:014:09:34:29
Block: 1400925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10302 RingCT/type: yes/0
Extra: 01257e0cb44744ee7a37171df19f2cc0d8bc2a7c96f298fe1bdbc88e227684d40d021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f5e8b1c7e70f0839e7175d0c62a535cd59e9ecc702dd721ea4045101f84729f 0.600000000000 1889244 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": 1400935, "vin": [ { "gen": { "height": 1400925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f5e8b1c7e70f0839e7175d0c62a535cd59e9ecc702dd721ea4045101f84729f" } } ], "extra": [ 1, 37, 126, 12, 180, 71, 68, 238, 122, 55, 23, 29, 241, 159, 44, 192, 216, 188, 42, 124, 150, 242, 152, 254, 27, 219, 200, 142, 34, 118, 132, 212, 13, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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