Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e330fe7acb688d73fbe066acd6a23a239222d368a29fe0fe2964d2bd321c91f4

Tx prefix hash: 486c7a7fd9ce3393f80e88aca3aa33cf92d141188b2a38e787ab305f45d6f296
Tx public key: 5d638edd34667b8fc9938b05603e8b636dbce4dbfb939f48f0dd6a5338dc528d
Timestamp: 1578103913 Timestamp [UTC]: 2020-01-04 02:11:53 Age [y:d:h:m:s]: 06:132:20:09:07
Block: 38159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1495748 RingCT/type: yes/0
Extra: 015d638edd34667b8fc9938b05603e8b636dbce4dbfb939f48f0dd6a5338dc528d021100000009d81c26c0000000000000000000

1 output(s) for total of 0.458853639276 xmr

stealth address amount amount idx tag
00: a8f20cb51d3cd1e684226f0c5c268a080f4db26f459172195b3fafd89284dc5c 0.458853639276 64926 of 0 -

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": 38169, "vin": [ { "gen": { "height": 38159 } } ], "vout": [ { "amount": 458853639276, "target": { "key": "a8f20cb51d3cd1e684226f0c5c268a080f4db26f459172195b3fafd89284dc5c" } } ], "extra": [ 1, 93, 99, 142, 221, 52, 102, 123, 143, 201, 147, 139, 5, 96, 62, 139, 99, 109, 188, 228, 219, 251, 147, 159, 72, 240, 221, 106, 83, 56, 220, 82, 141, 2, 17, 0, 0, 0, 9, 216, 28, 38, 192, 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: