Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 925a6f78687adad06032d45a7923daa4505cf7d379b746bb4b2b40d5de8de8b5

Tx prefix hash: 5dc42e7949f57f465932886674d11a2f71ab7f774a9aad0e1138e55502f08c0b
Tx public key: 6ba5ac318320e76d1a039e551c46a6f664651d52ab155a447b90b8fd4976eb63
Timestamp: 1742474530 Timestamp [UTC]: 2025-03-20 12:42:10 Age [y:d:h:m:s]: 01:055:22:32:07
Block: 1243431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290902 RingCT/type: yes/0
Extra: 016ba5ac318320e76d1a039e551c46a6f664651d52ab155a447b90b8fd4976eb63021100000001bfa77623000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 722de17a79a05a64204d3465beabd12482948a318bd3b0b749658b1594fe92e4 0.000600000000 1730416 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": 1243441, "vin": [ { "gen": { "height": 1243431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "722de17a79a05a64204d3465beabd12482948a318bd3b0b749658b1594fe92e4" } } ], "extra": [ 1, 107, 165, 172, 49, 131, 32, 231, 109, 26, 3, 158, 85, 28, 70, 166, 246, 100, 101, 29, 82, 171, 21, 90, 68, 123, 144, 184, 253, 73, 118, 235, 99, 2, 17, 0, 0, 0, 1, 191, 167, 118, 35, 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: