Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 937139897f4e989db41f7e9579b3229cc34b4c8d341da1253855a0f97431dda4

Tx prefix hash: 7afe3a7f8e2be23b7dbe8630bb4f49bc87e606cd7d49a407d33941278eeef93c
Tx public key: 7fd93d7ceabb16b59ecec675fa2e24392be9385bb3eb7d6f01a775cba95e8923
Timestamp: 1747558894 Timestamp [UTC]: 2025-05-18 09:01:34 Age [y:d:h:m:s]: 00:357:23:53:13
Block: 1285494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246035 RingCT/type: yes/0
Extra: 017fd93d7ceabb16b59ecec675fa2e24392be9385bb3eb7d6f01a775cba95e89230211000000011f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ec77a1f98552244c0a1759b339fb1ae40e18ddbbff3c451d79917d7d22fb4a98 0.000600000000 1772959 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": 1285504, "vin": [ { "gen": { "height": 1285494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec77a1f98552244c0a1759b339fb1ae40e18ddbbff3c451d79917d7d22fb4a98" } } ], "extra": [ 1, 127, 217, 61, 124, 234, 187, 22, 181, 158, 206, 198, 117, 250, 46, 36, 57, 43, 233, 56, 91, 179, 235, 125, 111, 1, 167, 117, 203, 169, 94, 137, 35, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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: