Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f389c999b01e5215e92dfbc35b52dd551cdd4eb0293128ae1c6c7010d08bdd10

Tx prefix hash: 833e1f011bea56095d41ea148dbc9d21d94c47ffa5f478d588ca77f3877d66c8
Tx public key: 00a1b9a5e1e54f20fd76e871c30bb9277147a8ccd0e54545e72794a62dc368d8
Timestamp: 1765156711 Timestamp [UCT]: 2025-12-08 01:18:31 Age [y:d:h:m:s]: 00:016:01:04:27
Block: 1428794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 11475 RingCT/type: yes/0
Extra: 0100a1b9a5e1e54f20fd76e871c30bb9277147a8ccd0e54545e72794a62dc368d802090000000dd48050ef00

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a520dc4dde3173a5080f3af3541ef2220a16cf4a615a1a93dd7d35591c7a0c8 0.600000000000 1917517 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": 1428804, "vin": [ { "gen": { "height": 1428794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a520dc4dde3173a5080f3af3541ef2220a16cf4a615a1a93dd7d35591c7a0c8" } } ], "extra": [ 1, 0, 161, 185, 165, 225, 229, 79, 32, 253, 118, 232, 113, 195, 11, 185, 39, 113, 71, 168, 204, 208, 229, 69, 69, 231, 39, 148, 166, 45, 195, 104, 216, 2, 9, 0, 0, 0, 13, 212, 128, 80, 239, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8