Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 055d996060c03dddec9649ac5c4cee1a145ae43d87f96d183e48bf63c18398fa

Tx prefix hash: ca53f07a2771327068b81d441db795f785bc28774cf1c8e11a60ecb31c2bff9d
Tx public key: 7967a8829aa390e68f6ff04574d152607c5b3960cceade12a712a4a22f44754e
Timestamp: 1773070414 Timestamp [UTC]: 2026-03-09 15:33:34 Age [y:d:h:m:s]: 00:256:11:32:03
Block: 1494153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188966 RingCT/type: yes/0
Extra: 017967a8829aa390e68f6ff04574d152607c5b3960cceade12a712a4a22f44754e021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7e506ece9fd5f36f809e736377a4444bf791b8691a7a5a1ac5ee6c948a24a177 0.000600000000 1983721 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": 1494163, "vin": [ { "gen": { "height": 1494153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e506ece9fd5f36f809e736377a4444bf791b8691a7a5a1ac5ee6c948a24a177" } } ], "extra": [ 1, 121, 103, 168, 130, 154, 163, 144, 230, 143, 111, 240, 69, 116, 209, 82, 96, 124, 91, 57, 96, 204, 234, 222, 18, 167, 18, 164, 162, 47, 68, 117, 78, 2, 17, 0, 0, 0, 7, 228, 245, 25, 63, 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: