Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6afa9b8348443679a7dc8f2d6cd0ddbb6afcb06318ae2a2a8e6d622b10b846c

Tx prefix hash: 44932952e9952187339c71b591e2afaa892de9606ac6bb585ca95e576a8c59e3
Tx public key: b8753451ee4d2c1986639fe212ac08f353e63dd1faa26f157bc9dc24ca03e24b
Timestamp: 1747948646 Timestamp [UTC]: 2025-05-22 21:17:26 Age [y:d:h:m:s]: 01:182:20:22:59
Block: 1288734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394760 RingCT/type: yes/0
Extra: 01b8753451ee4d2c1986639fe212ac08f353e63dd1faa26f157bc9dc24ca03e24b02110000000c9f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 96abdb344fb3016495932e9d8242b57337d051299d1fe2b8a69339e97a8136bc 0.000600000000 1776201 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": 1288744, "vin": [ { "gen": { "height": 1288734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96abdb344fb3016495932e9d8242b57337d051299d1fe2b8a69339e97a8136bc" } } ], "extra": [ 1, 184, 117, 52, 81, 238, 77, 44, 25, 134, 99, 159, 226, 18, 172, 8, 243, 83, 230, 61, 209, 250, 162, 111, 21, 123, 201, 220, 36, 202, 3, 226, 75, 2, 17, 0, 0, 0, 12, 159, 159, 230, 140, 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: