Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76c9861b9c8dfda95f3632a27c286b68e0b3f94a3a67113004285db45109aff6

Tx prefix hash: 2b34281912bb2acbe153f35a4b05a8461e46173615b226b994f0ce186559c69c
Tx public key: 41a5731b18624f151f49105d81ca010ff7323c5f67879ddb99fc8da7d9e64f4f
Timestamp: 1581667230 Timestamp [UTC]: 2020-02-14 08:00:30 Age [y:d:h:m:s]: 06:279:13:23:04
Block: 64733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1616661 RingCT/type: yes/0
Extra: 0141a5731b18624f151f49105d81ca010ff7323c5f67879ddb99fc8da7d9e64f4f021100000002026b59f3000000000000000000

1 output(s) for total of 0.374553198815 xmr

stealth address amount amount idx tag
00: ffae9df599a06541294077410b35423847b6e3b82ce80bb72901024b092103ad 0.374553198815 119411 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": 64743, "vin": [ { "gen": { "height": 64733 } } ], "vout": [ { "amount": 374553198815, "target": { "key": "ffae9df599a06541294077410b35423847b6e3b82ce80bb72901024b092103ad" } } ], "extra": [ 1, 65, 165, 115, 27, 24, 98, 79, 21, 31, 73, 16, 93, 129, 202, 1, 15, 247, 50, 60, 95, 103, 135, 157, 219, 153, 252, 141, 167, 217, 230, 79, 79, 2, 17, 0, 0, 0, 2, 2, 107, 89, 243, 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: