Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342ec3bd297a22760942880b617f005fdce954f3cdec46361c241dc1d0cea9d1

Tx prefix hash: 8569e98c42fa11bc39feca8b4282630d247628bb5f39f13528780ef303a84f4f
Tx public key: c8b0312f2663bf3bc61064e3d7bd8d146ef39a3da4fd2773adc7a67018476711
Timestamp: 1756917999 Timestamp [UTC]: 2025-09-03 16:46:39 Age [y:d:h:m:s]: 01:078:17:49:55
Block: 1360589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322767 RingCT/type: yes/0
Extra: 01c8b0312f2663bf3bc61064e3d7bd8d146ef39a3da4fd2773adc7a67018476711021100000006ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 239ced8ef58c012e6b93823adb556c4e7a5784ac8fba51a9ff5c518082790074 0.000600000000 1848602 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": 1360599, "vin": [ { "gen": { "height": 1360589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "239ced8ef58c012e6b93823adb556c4e7a5784ac8fba51a9ff5c518082790074" } } ], "extra": [ 1, 200, 176, 49, 47, 38, 99, 191, 59, 198, 16, 100, 227, 215, 189, 141, 20, 110, 243, 154, 61, 164, 253, 39, 115, 173, 199, 166, 112, 24, 71, 103, 17, 2, 17, 0, 0, 0, 6, 173, 121, 72, 208, 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: