Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 247900d42bd2d7db5cdca9a5935ae09dcbc29827b658f0ce42b7f35ab95388df

Tx prefix hash: 1cb31f274cc34046f0ec3249e34a46951a5faa5157a77e0d95dd8d3f25e18def
Tx public key: 10c51fc6c27e21f6cd18d7a6bf78509e8b3a24c0a6303e34bf79e9d1a37e817c
Timestamp: 1773503989 Timestamp [UTC]: 2026-03-14 15:59:49 Age [y:d:h:m:s]: 00:245:13:51:50
Block: 1497754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180928 RingCT/type: yes/0
Extra: 0110c51fc6c27e21f6cd18d7a6bf78509e8b3a24c0a6303e34bf79e9d1a37e817c021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f815da1cc9b66a9c38461cd45c4d5dc475d7223f76906bf5b01a969078dd9585 0.000600000000 1987392 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": 1497764, "vin": [ { "gen": { "height": 1497754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f815da1cc9b66a9c38461cd45c4d5dc475d7223f76906bf5b01a969078dd9585" } } ], "extra": [ 1, 16, 197, 31, 198, 194, 126, 33, 246, 205, 24, 215, 166, 191, 120, 80, 158, 139, 58, 36, 192, 166, 48, 62, 52, 191, 121, 233, 209, 163, 126, 129, 124, 2, 17, 0, 0, 0, 7, 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: