Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5cfb276fc2d441f8a326e6bf3a5f890fc833f3b36762433a324cdd067e9ac4a

Tx prefix hash: 04bf24655ea9adfff355353554096670bdfd6f4feb5e56b796f9c679952006b9
Tx public key: 803abb2a1d2243e0ec095742c8137ff2d0cb45335306ac1746ba0bcd1a578e44
Timestamp: 1764492468 Timestamp [UCT]: 2025-11-30 08:47:48 Age [y:d:h:m:s]: 00:033:22:46:01
Block: 1423300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24302 RingCT/type: yes/0
Extra: 01803abb2a1d2243e0ec095742c8137ff2d0cb45335306ac1746ba0bcd1a578e44021100000001da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68e2e0c85fe16873b7c9cef6bfb482eb798e4c9c3d2cb0b8f40db2c73a1fa4f4 0.600000000000 1911905 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": 1423310, "vin": [ { "gen": { "height": 1423300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68e2e0c85fe16873b7c9cef6bfb482eb798e4c9c3d2cb0b8f40db2c73a1fa4f4" } } ], "extra": [ 1, 128, 58, 187, 42, 29, 34, 67, 224, 236, 9, 87, 66, 200, 19, 127, 242, 208, 203, 69, 51, 83, 6, 172, 23, 70, 186, 11, 205, 26, 87, 142, 68, 2, 17, 0, 0, 0, 1, 218, 85, 72, 72, 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