Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e51c3b94896ea1213b8fe3e2283255445f65ec1ca67ffd91f06019ce00c265ec

Tx prefix hash: 3ccd776398d8f4c7071d88f321f9ca13b314c1e3a4c1ef26a5fd2698e5b6639f
Tx public key: 66de46086686ea4e1284f59c21b2df7970cde5c8bf85090f1d7254e01ed71b3c
Timestamp: 1580887323 Timestamp [UTC]: 2020-02-05 07:22:03 Age [y:d:h:m:s]: 06:290:11:29:30
Block: 58932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1623941 RingCT/type: yes/0
Extra: 0166de46086686ea4e1284f59c21b2df7970cde5c8bf85090f1d7254e01ed71b3c021100000002391a8d0e000000000000000000

1 output(s) for total of 0.391502590508 xmr

stealth address amount amount idx tag
00: f4378f5fab04f0228e175c775822f5ffae83661a29cd8e4b8d1cc960773fc8ad 0.391502590508 108880 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": 58942, "vin": [ { "gen": { "height": 58932 } } ], "vout": [ { "amount": 391502590508, "target": { "key": "f4378f5fab04f0228e175c775822f5ffae83661a29cd8e4b8d1cc960773fc8ad" } } ], "extra": [ 1, 102, 222, 70, 8, 102, 134, 234, 78, 18, 132, 245, 156, 33, 178, 223, 121, 112, 205, 229, 200, 191, 133, 9, 15, 29, 114, 84, 224, 30, 215, 27, 60, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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: