Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa9edd0b8b39ae4876bfbdc01ba93baed650bd17defac67bbdcbe07aec165137

Tx prefix hash: 092a9a19d1b1ab2737d391977cdc3071d0edcb5cf2812483b27facc22e930889
Tx public key: b7508667450a14412b2f337e8afefb788073ab02a6df0d9eca0d6cc1dd9324e6
Timestamp: 1748729261 Timestamp [UTC]: 2025-05-31 22:07:41 Age [y:d:h:m:s]: 01:164:14:42:52
Block: 1295194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381444 RingCT/type: yes/0
Extra: 01b7508667450a14412b2f337e8afefb788073ab02a6df0d9eca0d6cc1dd9324e602110000000443846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b68a44cbe4e91ab01bd2a9f032eb7b03f1eb25d7593f98715c29aed423b5bc3d 0.000600000000 1782697 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": 1295204, "vin": [ { "gen": { "height": 1295194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b68a44cbe4e91ab01bd2a9f032eb7b03f1eb25d7593f98715c29aed423b5bc3d" } } ], "extra": [ 1, 183, 80, 134, 103, 69, 10, 20, 65, 43, 47, 51, 126, 138, 254, 251, 120, 128, 115, 171, 2, 166, 223, 13, 158, 202, 13, 108, 193, 221, 147, 36, 230, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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: