Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfd9037a92d95669c06dd8f78bd1feba1672e333866a91d9d55805df51aa3424

Tx prefix hash: 9fa9316ab23878c1a12efd6d8896029ec1efcc429c71bc962b06173ed0d5c204
Tx public key: 0a89e53ab28f7330bc6a14e7bb8874462a4267de5585a4ab1ca2ef8b02a61393
Timestamp: 1744586962 Timestamp [UTC]: 2025-04-13 23:29:22 Age [y:d:h:m:s]: 01:220:21:36:25
Block: 1260908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422028 RingCT/type: yes/0
Extra: 010a89e53ab28f7330bc6a14e7bb8874462a4267de5585a4ab1ca2ef8b02a61393021100000002dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf05cd4ee94bd15fd922a85c7cc5d0bef0a1614b61f551a4c264462335ef09d6 0.000600000000 1748073 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 dinastycoin-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": 1260918, "vin": [ { "gen": { "height": 1260908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf05cd4ee94bd15fd922a85c7cc5d0bef0a1614b61f551a4c264462335ef09d6" } } ], "extra": [ 1, 10, 137, 229, 58, 178, 143, 115, 48, 188, 106, 20, 231, 187, 136, 116, 70, 42, 66, 103, 222, 85, 133, 164, 171, 28, 162, 239, 139, 2, 166, 19, 147, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: