Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fda8760c3ecc4026efd5e97080f71860ac8a1226f262bfa54009189ad068b67

Tx prefix hash: 2aa9ea74d71b637a4a2276fdd5eff583a39e0c79d890b5a27e43be6a8bf1f47b
Tx public key: 62785b86ef9855596877eabfb29b61da624a1d999ac40b4712fb763e70794984
Timestamp: 1705697263 Timestamp [UTC]: 2024-01-19 20:47:43 Age [y:d:h:m:s]: 02:306:04:39:43
Block: 938953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 744123 RingCT/type: yes/0
Extra: 0162785b86ef9855596877eabfb29b61da624a1d999ac40b4712fb763e7079498402110000000652d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8bc3b6594f46198dc53c0ba01b91cdc2d3be2666bbfba336e900f5095d609afd 0.000600000000 1397037 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": 938963, "vin": [ { "gen": { "height": 938953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bc3b6594f46198dc53c0ba01b91cdc2d3be2666bbfba336e900f5095d609afd" } } ], "extra": [ 1, 98, 120, 91, 134, 239, 152, 85, 89, 104, 119, 234, 191, 178, 155, 97, 218, 98, 74, 29, 153, 154, 196, 11, 71, 18, 251, 118, 62, 112, 121, 73, 132, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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: