Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e742e37e42e4f111e1763445c5f9933e6cab0c47e9c0b2e10775e3c48c27c1d2

Tx prefix hash: 0747f20c7a0a389bd6781dc4f29f7caf03baf14f3195e3a75b2cda3050e0b6f6
Tx public key: 5f0cfb85226f3d1b573d851a4ad7475074fe6c17851f5181fbc8ff22ae24f290
Timestamp: 1774187862 Timestamp [UTC]: 2026-03-22 13:57:42 Age [y:d:h:m:s]: 00:238:16:03:17
Block: 1503391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176052 RingCT/type: yes/0
Extra: 015f0cfb85226f3d1b573d851a4ad7475074fe6c17851f5181fbc8ff22ae24f290021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4fad6fddfaa440555a7f09280bfb47a6532674cd2dd8268b2fb0ba43f2d292d0 0.000600000000 1993101 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": 1503401, "vin": [ { "gen": { "height": 1503391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fad6fddfaa440555a7f09280bfb47a6532674cd2dd8268b2fb0ba43f2d292d0" } } ], "extra": [ 1, 95, 12, 251, 133, 34, 111, 61, 27, 87, 61, 133, 26, 74, 215, 71, 80, 116, 254, 108, 23, 133, 31, 81, 129, 251, 200, 255, 34, 174, 36, 242, 144, 2, 17, 0, 0, 0, 7, 241, 136, 200, 168, 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: