Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6046738214335fcf452911fbd9c03454900a3c9abade846a4a8bb1592a314659

Tx prefix hash: 93fdaffee2dd97ce0bc705846787ae277d50bcd85717a8e4833c677fab4b950f
Tx public key: ef13b7d86e68ba60605b8731a10d988753c1e0d9a95a6126f1de2a3c377c8e3f
Timestamp: 1761289296 Timestamp [UTC]: 2025-10-24 07:01:36 Age [y:d:h:m:s]: 00:200:18:43:08
Block: 1396760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135753 RingCT/type: yes/0
Extra: 01ef13b7d86e68ba60605b8731a10d988753c1e0d9a95a6126f1de2a3c377c8e3f021100000008e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf8ec2a4acc4b9d9c6686e2839f2b7cda104094a2a7204cc9e677a84847766fb 0.000600000000 1885047 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": 1396770, "vin": [ { "gen": { "height": 1396760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf8ec2a4acc4b9d9c6686e2839f2b7cda104094a2a7204cc9e677a84847766fb" } } ], "extra": [ 1, 239, 19, 183, 216, 110, 104, 186, 96, 96, 91, 135, 49, 161, 13, 152, 135, 83, 193, 224, 217, 169, 90, 97, 38, 241, 222, 42, 60, 55, 124, 142, 63, 2, 17, 0, 0, 0, 8, 228, 220, 144, 9, 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: