Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30b19af69eb593939faecf20617dba7ef19d36f573f29b9ccd831308ba679d4e

Tx prefix hash: 8dd5a936122c2fdbd2b30db5e92643be30fd7324c95e90c955e3ed898f0d08cb
Tx public key: 8e0d45e0a114fd8cdc2138576c2f9cbbec6b810a02870e08fc0b19e5081e14b2
Timestamp: 1762285677 Timestamp [UCT]: 2025-11-04 19:47:57 Age [y:d:h:m:s]: 00:033:07:58:56
Block: 1405009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23861 RingCT/type: yes/0
Extra: 018e0d45e0a114fd8cdc2138576c2f9cbbec6b810a02870e08fc0b19e5081e14b2021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6860dc6f1f04b4a93136210ba497110f44ae43d85e334b6648251a0229c6657 0.600000000000 1893378 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": 1405019, "vin": [ { "gen": { "height": 1405009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6860dc6f1f04b4a93136210ba497110f44ae43d85e334b6648251a0229c6657" } } ], "extra": [ 1, 142, 13, 69, 224, 161, 20, 253, 140, 220, 33, 56, 87, 108, 47, 156, 187, 236, 107, 129, 10, 2, 135, 14, 8, 252, 11, 25, 229, 8, 30, 20, 178, 2, 17, 0, 0, 0, 4, 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