Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f20594ebbd2397fbe0a06bf6e8a770ee8221c76a00188c9e9564dd93d27183e

Tx prefix hash: 29c2293f12b4b18670babe0f587d6745defaa3f44d0075ab8d5792bb02b991c1
Tx public key: 1cc98bfb6de34d540449ae695b77ae7f3a37c17b9283f5106791a5321d62f438
Timestamp: 1740704202 Timestamp [UTC]: 2025-02-28 00:56:42 Age [y:d:h:m:s]: 01:177:21:22:14
Block: 1228733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391514 RingCT/type: yes/0
Extra: 011cc98bfb6de34d540449ae695b77ae7f3a37c17b9283f5106791a5321d62f4380211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 940228fd18af49540d9c491c19ee0f9858ec308467c70163a10eba7b772c217c 0.000600000000 1715614 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": 1228743, "vin": [ { "gen": { "height": 1228733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "940228fd18af49540d9c491c19ee0f9858ec308467c70163a10eba7b772c217c" } } ], "extra": [ 1, 28, 201, 139, 251, 109, 227, 77, 84, 4, 73, 174, 105, 91, 119, 174, 127, 58, 55, 193, 123, 146, 131, 245, 16, 103, 145, 165, 50, 29, 98, 244, 56, 2, 17, 0, 0, 0, 2, 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: