Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 385aae509b095aec2926008281333fd31fac9f7865205b519847cee30bbcb3df

Tx prefix hash: 2872589f7b1b7011293671ff87242ec3222163e1c50955e8ce4c088d498ad5c5
Tx public key: de9df0367df63b07cb32ec26e53c583ab9ec7c28cc3fa2161160e7e16e59d0ef
Timestamp: 1744653293 Timestamp [UTC]: 2025-04-14 17:54:53 Age [y:d:h:m:s]: 01:032:18:14:27
Block: 1261446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274416 RingCT/type: yes/0
Extra: 01de9df0367df63b07cb32ec26e53c583ab9ec7c28cc3fa2161160e7e16e59d0ef0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a5cc3d344351623ceab23b8b2dcf76055b62738c23bd397b004347d75fde97d 0.000600000000 1748617 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": 1261456, "vin": [ { "gen": { "height": 1261446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a5cc3d344351623ceab23b8b2dcf76055b62738c23bd397b004347d75fde97d" } } ], "extra": [ 1, 222, 157, 240, 54, 125, 246, 59, 7, 203, 50, 236, 38, 229, 60, 88, 58, 185, 236, 124, 40, 204, 63, 162, 22, 17, 96, 231, 225, 110, 89, 208, 239, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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: