Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f623bff2a4edb94a803e8cec81d7185abd5e56e8a506b6afeae9b82b31295c7

Tx prefix hash: 6dce6c546ef4b0e325e1590e66e8c6619a157ac5d914c398b9fdbd2d69c64e25
Tx public key: daef299e865bebc1c510365055cb53e660f8dc88cb37d7643c3d2bb12b95e504
Timestamp: 1761857736 Timestamp [UCT]: 2025-10-30 20:55:36 Age [y:d:h:m:s]: 00:068:07:57:59
Block: 1401466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48916 RingCT/type: yes/0
Extra: 01daef299e865bebc1c510365055cb53e660f8dc88cb37d7643c3d2bb12b95e504021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0224d81e45c3e23a49d423c6204f34dcb2a9c1ada90cb1fcba40f067ea3c0352 0.600000000000 1889785 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": 1401476, "vin": [ { "gen": { "height": 1401466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0224d81e45c3e23a49d423c6204f34dcb2a9c1ada90cb1fcba40f067ea3c0352" } } ], "extra": [ 1, 218, 239, 41, 158, 134, 91, 235, 193, 197, 16, 54, 80, 85, 203, 83, 230, 96, 248, 220, 136, 203, 55, 215, 100, 60, 61, 43, 177, 43, 149, 229, 4, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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