Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91ba2c802170317bc38473f5c7299f5e5ad50d1af611b22dad938bc3e69f7365

Tx prefix hash: cc94552bd68ecaef8fdf9fad03789b6a62c1b84f154d5e2e5fdf56ac399c8bb2
Tx public key: cdd5778b09f77647411810f54d24dca6d18e55c380773ce70497c86a3241d3b3
Timestamp: 1763219053 Timestamp [UCT]: 2025-11-15 15:04:13 Age [y:d:h:m:s]: 00:012:16:11:09
Block: 1412733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9078 RingCT/type: yes/0
Extra: 01cdd5778b09f77647411810f54d24dca6d18e55c380773ce70497c86a3241d3b3021100000002fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c8704b5c820d10804e3ca07bf87a3d2ae7f8b02f9f029395bc3cba64f430c40 0.600000000000 1901206 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": 1412743, "vin": [ { "gen": { "height": 1412733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c8704b5c820d10804e3ca07bf87a3d2ae7f8b02f9f029395bc3cba64f430c40" } } ], "extra": [ 1, 205, 213, 119, 139, 9, 247, 118, 71, 65, 24, 16, 245, 77, 36, 220, 166, 209, 142, 85, 195, 128, 119, 60, 231, 4, 151, 200, 106, 50, 65, 211, 179, 2, 17, 0, 0, 0, 2, 251, 143, 208, 137, 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