Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa8a69f4ae5bd149fd258ac3193510ac023bb64d4c3058a04034297c19a8b6f3

Tx prefix hash: c1dcfef36359bc97e41d7b99840015f8aa380a643c285579e3d4fcd9f53c66af
Tx public key: 19e981af36ef6e199e29012be41839c72c8a5e4e3dd7d0784a93f5ae456b19f0
Timestamp: 1747000853 Timestamp [UTC]: 2025-05-11 22:00:53 Age [y:d:h:m:s]: 01:062:14:00:26
Block: 1280874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300458 RingCT/type: yes/0
Extra: 0119e981af36ef6e199e29012be41839c72c8a5e4e3dd7d0784a93f5ae456b19f0021100000001e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4c761638295a489aa1f7c812dba0fc37b2cf07817c66b8ecd852d3079d6a60e2 0.000600000000 1768267 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": 1280884, "vin": [ { "gen": { "height": 1280874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c761638295a489aa1f7c812dba0fc37b2cf07817c66b8ecd852d3079d6a60e2" } } ], "extra": [ 1, 25, 233, 129, 175, 54, 239, 110, 25, 158, 41, 1, 43, 228, 24, 57, 199, 44, 138, 94, 78, 61, 215, 208, 120, 74, 147, 245, 174, 69, 107, 25, 240, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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: