Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a53692324adf4ba45aff64ab6c52cd9bbbb8429a1c847dcfbca581368aa5695

Tx prefix hash: 4f5d14a786c47cecf6526212d50927b2c62550fe4d698d042f01e68d520925ea
Tx public key: e5b3ce3386a8e1115acac2e74106c831a569aac2e9ce9c8d2df5f7ba4e75092a
Timestamp: 1707462278 Timestamp [UTC]: 2024-02-09 07:04:38 Age [y:d:h:m:s]: 02:284:13:20:39
Block: 953601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 728538 RingCT/type: yes/0
Extra: 01e5b3ce3386a8e1115acac2e74106c831a569aac2e9ce9c8d2df5f7ba4e75092a02110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2aa0d239bda6a8b33f2325257a9dfbd08d81583430bd87bf1229b8be26c16f77 0.000600000000 1412835 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": 953611, "vin": [ { "gen": { "height": 953601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aa0d239bda6a8b33f2325257a9dfbd08d81583430bd87bf1229b8be26c16f77" } } ], "extra": [ 1, 229, 179, 206, 51, 134, 168, 225, 17, 90, 202, 194, 231, 65, 6, 200, 49, 165, 105, 170, 194, 233, 206, 156, 141, 45, 245, 247, 186, 78, 117, 9, 42, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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: