Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50f79fb4439ed7426c080d2e4cb52255422e93b7b520a05b89ee7da5546fa320

Tx prefix hash: 0e08c6f9efa76fabecb211ad954dce441df30b843afddcdc758234693ed67cc9
Tx public key: 6e32f09f9d043364047c29105a6ec3bb565d9e36ed5b408d2e82c4a8fcf26b67
Timestamp: 1747376285 Timestamp [UTC]: 2025-05-16 06:18:05 Age [y:d:h:m:s]: 00:359:21:42:23
Block: 1283983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247546 RingCT/type: yes/0
Extra: 016e32f09f9d043364047c29105a6ec3bb565d9e36ed5b408d2e82c4a8fcf26b670211000000011f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c7c7f21f526e3fdd47b645e2bf37967e29fe60070b2bb45ae4ab4f6a6fcec9e3 0.000600000000 1771418 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": 1283993, "vin": [ { "gen": { "height": 1283983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7c7f21f526e3fdd47b645e2bf37967e29fe60070b2bb45ae4ab4f6a6fcec9e3" } } ], "extra": [ 1, 110, 50, 240, 159, 157, 4, 51, 100, 4, 124, 41, 16, 90, 110, 195, 187, 86, 93, 158, 54, 237, 91, 64, 141, 46, 130, 196, 168, 252, 242, 107, 103, 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: