Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93900dcfb182da845d36e62d7249dc7eef2ac7c74f92dd0c5d3ccedffff10ae3

Tx prefix hash: 80879c6757677e0d56fe5d7a75e9eccceb307fb1240acf3a529463e43d00e89e
Tx public key: 22f6918f2d9b98e3894c257795b6974b4583b02e5b2653dbac2ce200e90e7698
Timestamp: 1735836626 Timestamp [UTC]: 2025-01-02 16:50:26 Age [y:d:h:m:s]: 01:317:17:26:57
Block: 1188716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490865 RingCT/type: yes/0
Extra: 0122f6918f2d9b98e3894c257795b6974b4583b02e5b2653dbac2ce200e90e76980211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 84c9e58f9231e199163c9c62dde35eb2e4b1a6de241fcf08aa1d53b84ea8e9f2 0.000600000000 1675219 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": 1188726, "vin": [ { "gen": { "height": 1188716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84c9e58f9231e199163c9c62dde35eb2e4b1a6de241fcf08aa1d53b84ea8e9f2" } } ], "extra": [ 1, 34, 246, 145, 143, 45, 155, 152, 227, 137, 76, 37, 119, 149, 182, 151, 75, 69, 131, 176, 46, 91, 38, 83, 219, 172, 44, 226, 0, 233, 14, 118, 152, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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: