Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89b566b09387929655c972c30b9a572831a0dc3605bfddbd99c3d6f2a9473f4f

Tx prefix hash: 67b01abc5d3e4029fa7ff7977fbff1970b3d3a4a7878bd78654d24f5ad8952fe
Tx public key: f4a9a42f51c2f20960a18c9942f17a76109db94e5e92d29275025f11e2ee7b66
Timestamp: 1751434074 Timestamp [UCT]: 2025-07-02 05:27:54 Age [y:d:h:m:s]: 00:130:16:37:21
Block: 1317030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91627 RingCT/type: yes/0
Extra: 01f4a9a42f51c2f20960a18c9942f17a76109db94e5e92d29275025f11e2ee7b6602110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 662122614a2f9f0be4b3950205dfa7d00c6cf5300886c20ec905577c3aaddd63 0.600000000000 1804695 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": 1317040, "vin": [ { "gen": { "height": 1317030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "662122614a2f9f0be4b3950205dfa7d00c6cf5300886c20ec905577c3aaddd63" } } ], "extra": [ 1, 244, 169, 164, 47, 81, 194, 242, 9, 96, 161, 140, 153, 66, 241, 122, 118, 16, 157, 185, 78, 94, 146, 210, 146, 117, 2, 95, 17, 226, 238, 123, 102, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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