Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0864f218c4d3fc85df4fb33a61b5935170a2ec4f847e69ed957bb0a4a23e49a

Tx prefix hash: f04cf5023323825004ea1eea7aff781b2ff5ff3859119aee4b9d13aeea150a23
Tx public key: a5900e1759d7ee3c651513306d4b8630d1d53d9245a344a2bd56bd11b1ebd7d7
Timestamp: 1712260430 Timestamp [UTC]: 2024-04-04 19:53:50 Age [y:d:h:m:s]: 02:225:12:37:31
Block: 993377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 686149 RingCT/type: yes/0
Extra: 01a5900e1759d7ee3c651513306d4b8630d1d53d9245a344a2bd56bd11b1ebd7d702110000000352d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e95dc16ef770af48aac5c1cf2d5136bc483c0db5c287f9e39d1f748fe538fd18 0.000600000000 1453763 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": 993387, "vin": [ { "gen": { "height": 993377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e95dc16ef770af48aac5c1cf2d5136bc483c0db5c287f9e39d1f748fe538fd18" } } ], "extra": [ 1, 165, 144, 14, 23, 89, 215, 238, 60, 101, 21, 19, 48, 109, 75, 134, 48, 209, 213, 61, 146, 69, 163, 68, 162, 189, 86, 189, 17, 177, 235, 215, 215, 2, 17, 0, 0, 0, 3, 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: