Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5515a2e940ec46a167a30c782af8f6dc7d24ea18518484bf1d0c97f014f22b29

Tx prefix hash: a5ad1a54d14cfb1223431ca9e54ec572e3a7b286de4750b635361528f2f22eca
Tx public key: 7c29edcff41c0ee1f0f43623f537fe1419979cdf7d9cfedcb41e2daa792e1766
Timestamp: 1646585992 Timestamp [UTC]: 2022-03-06 16:59:52 Age [y:d:h:m:s]: 04:172:03:06:17
Block: 452686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1167494 RingCT/type: yes/0
Extra: 017c29edcff41c0ee1f0f43623f537fe1419979cdf7d9cfedcb41e2daa792e17660211000000225eb576c5000000000000000000

1 output(s) for total of 0.019411702999 xmr

stealth address amount amount idx tag
00: 66556f45fc80d39d683bd3efb7463f909d1321283ced61acf26a789e9746be80 0.019411702999 868037 of 0 -

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": 452696, "vin": [ { "gen": { "height": 452686 } } ], "vout": [ { "amount": 19411702999, "target": { "key": "66556f45fc80d39d683bd3efb7463f909d1321283ced61acf26a789e9746be80" } } ], "extra": [ 1, 124, 41, 237, 207, 244, 28, 14, 225, 240, 244, 54, 35, 245, 55, 254, 20, 25, 151, 156, 223, 125, 156, 254, 220, 180, 30, 45, 170, 121, 46, 23, 102, 2, 17, 0, 0, 0, 34, 94, 181, 118, 197, 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: