Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79768cc29e0fd5ea3baa5c93d80ce41fb25a673c95caf06bd11d74799ea1322b

Tx prefix hash: 8c345cf0ad4f2e8d961857480049357a2405b340f0d4444978c93146610176b8
Tx public key: 48404dcc179619ec9aeb9f04a47d44b8fed3d53bf218be5f7ea8f2df373c7c15
Timestamp: 1743286950 Timestamp [UTC]: 2025-03-29 22:22:30 Age [y:d:h:m:s]: 01:041:08:38:03
Block: 1250132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280794 RingCT/type: yes/0
Extra: 0148404dcc179619ec9aeb9f04a47d44b8fed3d53bf218be5f7ea8f2df373c7c150211000000041a970403000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 595d027a94b39e6f327218fd4ab13f0dc9d1d6d97779cfd07f8c7c4bd01e8ce8 0.000600000000 1737179 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": 1250142, "vin": [ { "gen": { "height": 1250132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "595d027a94b39e6f327218fd4ab13f0dc9d1d6d97779cfd07f8c7c4bd01e8ce8" } } ], "extra": [ 1, 72, 64, 77, 204, 23, 150, 25, 236, 154, 235, 159, 4, 164, 125, 68, 184, 254, 211, 213, 59, 242, 24, 190, 95, 126, 168, 242, 223, 55, 60, 124, 21, 2, 17, 0, 0, 0, 4, 26, 151, 4, 3, 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: