Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbc30c811263ab8712d0d5da706547b4e312a6ad4a778ee1e88a903e71195dbb

Tx prefix hash: 961a75a2ef0a0a38b3115d8e6df2a3501934535a46f32087841368296fd773fe
Tx public key: 6bba80f87f45341b0f8802c8eb5e6e17f54d68a6fbd5dc161b057fbb8cb702d5
Timestamp: 1771465091 Timestamp [UTC]: 2026-02-19 01:38:11 Age [y:d:h:m:s]: 00:272:11:02:27
Block: 1480878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200256 RingCT/type: yes/0
Extra: 016bba80f87f45341b0f8802c8eb5e6e17f54d68a6fbd5dc161b057fbb8cb702d502110000000de4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d7249ad2a5085e3bcda31dbd30517646a1d67faf3f356cc56a693c9ce52d2b55 0.000600000000 1970250 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": 1480888, "vin": [ { "gen": { "height": 1480878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7249ad2a5085e3bcda31dbd30517646a1d67faf3f356cc56a693c9ce52d2b55" } } ], "extra": [ 1, 107, 186, 128, 248, 127, 69, 52, 27, 15, 136, 2, 200, 235, 94, 110, 23, 245, 77, 104, 166, 251, 213, 220, 22, 27, 5, 127, 187, 140, 183, 2, 213, 2, 17, 0, 0, 0, 13, 228, 245, 25, 63, 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: