Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 780164dbd03b69a0a2f360750dc0d5db5c91a1c0bba9651a0bdaf14c35d0c0ea

Tx prefix hash: 448d2e0d262ed31e44dfcaae7b4b834db2a155ad1ac8863938532df437593416
Tx public key: c3118ec1338aa1dc3b09def0cf9e44c15f21a052dd33a6343a2330ab868fca96
Timestamp: 1595478657 Timestamp [UTC]: 2020-07-23 04:30:57 Age [y:d:h:m:s]: 06:033:12:05:59
Block: 119648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1500421 RingCT/type: yes/0
Extra: 01c3118ec1338aa1dc3b09def0cf9e44c15f21a052dd33a6343a2330ab868fca9602110000001c4943cd9f000000000000000000

1 output(s) for total of 0.246352651897 xmr

stealth address amount amount idx tag
00: 3ce9a5cad5fd108edd7c4b8e83a550fa7b6331888c8c36b043a59f4f357e032e 0.246352651897 203940 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": 119658, "vin": [ { "gen": { "height": 119648 } } ], "vout": [ { "amount": 246352651897, "target": { "key": "3ce9a5cad5fd108edd7c4b8e83a550fa7b6331888c8c36b043a59f4f357e032e" } } ], "extra": [ 1, 195, 17, 142, 193, 51, 138, 161, 220, 59, 9, 222, 240, 207, 158, 68, 193, 95, 33, 160, 82, 221, 51, 166, 52, 58, 35, 48, 171, 134, 143, 202, 150, 2, 17, 0, 0, 0, 28, 73, 67, 205, 159, 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: