Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864d27a7e5d9adb99cf9a80c549880ee698ca1ecc5a8d5da32a6598a0f0a0a51

Tx prefix hash: c706c0751310feae3d6de993383d9bef6365e42c7141c89eb82e13c1abc57df3
Tx public key: c13a8d37b892a14f500805f57364465a4174303dc76bb929b2d90ae35a567762
Timestamp: 1579264342 Timestamp [UTC]: 2020-01-17 12:32:22 Age [y:d:h:m:s]: 06:309:19:43:48
Block: 47563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1635715 RingCT/type: yes/0
Extra: 01c13a8d37b892a14f500805f57364465a4174303dc76bb929b2d90ae35a567762021100000004d81c26c0000000000000000000

1 output(s) for total of 0.426984735128 xmr

stealth address amount amount idx tag
00: 44e269e2d15ed710d9a43cec7d65d14edbe187240c93bd26e958481aebdf16e9 0.426984735128 87890 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": 47573, "vin": [ { "gen": { "height": 47563 } } ], "vout": [ { "amount": 426984735128, "target": { "key": "44e269e2d15ed710d9a43cec7d65d14edbe187240c93bd26e958481aebdf16e9" } } ], "extra": [ 1, 193, 58, 141, 55, 184, 146, 161, 79, 80, 8, 5, 245, 115, 100, 70, 90, 65, 116, 48, 61, 199, 107, 185, 41, 178, 217, 10, 227, 90, 86, 119, 98, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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: