Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f08e0a8b3b2a1f8f9d4bba3ab90415732c63e37dbd4d8fd905ed931f8880aa12

Tx prefix hash: 15e4441e70f4b167a218d646ae1d28aa851b83bfd11e2460cce8b94c3f8994b7
Tx public key: 3167a43f134c26f8cbb3dd52815be119cef0e28d226cda6b4f3e62fa427a3fae
Timestamp: 1741516680 Timestamp [UTC]: 2025-03-09 10:38:00 Age [y:d:h:m:s]: 01:064:21:31:01
Block: 1235488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297227 RingCT/type: yes/0
Extra: 013167a43f134c26f8cbb3dd52815be119cef0e28d226cda6b4f3e62fa427a3fae02110000001f1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b500cee151fa5d07a0270393c42878fab911a14432870a143ec249f2b887340a 0.000600000000 1722427 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": 1235498, "vin": [ { "gen": { "height": 1235488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b500cee151fa5d07a0270393c42878fab911a14432870a143ec249f2b887340a" } } ], "extra": [ 1, 49, 103, 164, 63, 19, 76, 38, 248, 203, 179, 221, 82, 129, 91, 225, 25, 206, 240, 226, 141, 34, 108, 218, 107, 79, 62, 98, 250, 66, 122, 63, 174, 2, 17, 0, 0, 0, 31, 31, 10, 83, 235, 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: