Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0491b26c3bab3aabe671a6736acb1ecfdba1ada962c7d16f07db554e45df54bf

Tx prefix hash: 857cc6b92f0425df5040a20a5f4303542b378725e3ba92baf9f802360127028c
Tx public key: f1dc3f94bea583ab3d1d5e9d6868e6aa65e418c59d6dc602a8c1735257acf8a6
Timestamp: 1786654328 Timestamp [UTC]: 2026-08-13 20:52:08 Age [y:d:h:m:s]: 00:095:05:11:15
Block: 1612648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 67419 RingCT/type: yes/0
Extra: 01f1dc3f94bea583ab3d1d5e9d6868e6aa65e418c59d6dc602a8c1735257acf8a6

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 463ed5bec1a7c7f96056b9da6f8ffd9d0a39f8ff10cfdbe194f2b9f89c6105c4 0.000600000000 2102668 of 15 <e4>

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": 1612658, "vin": [ { "gen": { "height": 1612648 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "463ed5bec1a7c7f96056b9da6f8ffd9d0a39f8ff10cfdbe194f2b9f89c6105c4", "view_tag": "e4" } } } ], "extra": [ 1, 241, 220, 63, 148, 190, 165, 131, 171, 61, 29, 94, 157, 104, 104, 230, 170, 101, 228, 24, 197, 157, 109, 198, 2, 168, 193, 115, 82, 87, 172, 248, 166 ], "rct_signatures": { "type": 0 } }


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