Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 284aeec33907200aecd9d6496f20fc47fc170e074cf05d7b4efca7ec3054d2a9

Tx prefix hash: 672e6b7e82aaf5842945b1f729f5840afac8d9a875d5d0b2505a87368fc7a8fb
Tx public key: 2249b61338fb9be63d54f0fdf0a384051bef978c017cc5474c855d8712b0b9b3
Timestamp: 1775155654 Timestamp [UTC]: 2026-04-02 18:47:34 Age [y:d:h:m:s]: 00:231:12:06:39
Block: 1511408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171078 RingCT/type: yes/0
Extra: 012249b61338fb9be63d54f0fdf0a384051bef978c017cc5474c855d8712b0b9b3021100000001e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 94ae4e49b160db01938a3873aa855275c66ce624354afe7dfd91cdf16220a921 0.000600000000 2001200 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": 1511418, "vin": [ { "gen": { "height": 1511408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94ae4e49b160db01938a3873aa855275c66ce624354afe7dfd91cdf16220a921" } } ], "extra": [ 1, 34, 73, 182, 19, 56, 251, 155, 230, 61, 84, 240, 253, 240, 163, 132, 5, 27, 239, 151, 140, 1, 124, 197, 71, 76, 133, 93, 135, 18, 176, 185, 179, 2, 17, 0, 0, 0, 1, 227, 215, 220, 159, 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: