Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da938dc495af1ff54dd2bab8615afca281aacef2bb21cffdd87f8bdea7e64cd6

Tx prefix hash: 7602b384ef57c48e9950e1628e0e1b9df8d7a2f332f058477372c07cf9d9d365
Tx public key: b718fe45cac3d1e92fa1446044379afab56565abe24b745af1e44da25a10fcf1
Timestamp: 1772857044 Timestamp [UTC]: 2026-03-07 04:17:24 Age [y:d:h:m:s]: 00:257:11:55:38
Block: 1492395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189608 RingCT/type: yes/0
Extra: 01b718fe45cac3d1e92fa1446044379afab56565abe24b745af1e44da25a10fcf1021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4378cd8e67c11f701211a1d0ced2fa3f2dc0e162d497c9d6f2d98c61def6847e 0.000600000000 1981939 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": 1492405, "vin": [ { "gen": { "height": 1492395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4378cd8e67c11f701211a1d0ced2fa3f2dc0e162d497c9d6f2d98c61def6847e" } } ], "extra": [ 1, 183, 24, 254, 69, 202, 195, 209, 233, 47, 161, 68, 96, 68, 55, 154, 250, 181, 101, 101, 171, 226, 75, 116, 90, 241, 228, 77, 162, 90, 16, 252, 241, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: