Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53a940ae071d7faa60e2239d33b41b99ec8f01c404a86f0343f519f0fe16668e

Tx prefix hash: 1f4d919266c8a6e109336ea56524a1f7e82329348a38e4217d9d01a45e692330
Tx public key: 386f38caa536d2afd2830d5339941e27ebc2cd150713054fb04c8f18ceafaa74
Timestamp: 1761234340 Timestamp [UTC]: 2025-10-23 15:45:40 Age [y:d:h:m:s]: 00:204:11:52:12
Block: 1396300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138540 RingCT/type: yes/0
Extra: 01386f38caa536d2afd2830d5339941e27ebc2cd150713054fb04c8f18ceafaa74021100000002e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e5488888318a146de58bc46428125f18f7df9e8b1158c63f93a193b51d84bb52 0.000600000000 1884585 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": 1396310, "vin": [ { "gen": { "height": 1396300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5488888318a146de58bc46428125f18f7df9e8b1158c63f93a193b51d84bb52" } } ], "extra": [ 1, 56, 111, 56, 202, 165, 54, 210, 175, 210, 131, 13, 83, 57, 148, 30, 39, 235, 194, 205, 21, 7, 19, 5, 79, 176, 76, 143, 24, 206, 175, 170, 116, 2, 17, 0, 0, 0, 2, 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: