Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 288900f0b0206417d771eddf0b2b238f2e06e75ccf8181a9276f20fa3e8f807b

Tx prefix hash: 0771bbf8aa2d7df08ffca82d56a86f69f16723481ff44a0d9b4c1bbc35e956c3
Tx public key: 740426c9c9a4acf049863e27f92c05b54574d3bfb882b12d3f13b7cf2221decb
Timestamp: 1758077041 Timestamp [UTC]: 2025-09-17 02:44:01 Age [y:d:h:m:s]: 00:235:16:37:17
Block: 1370113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161179 RingCT/type: yes/0
Extra: 01740426c9c9a4acf049863e27f92c05b54574d3bfb882b12d3f13b7cf2221decb021100000004ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8aea52cfa4e2ed0c981d3e1ae983ecd345d45fc5942778f2b3dd8c4499e8a4c5 0.000600000000 1858188 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": 1370123, "vin": [ { "gen": { "height": 1370113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aea52cfa4e2ed0c981d3e1ae983ecd345d45fc5942778f2b3dd8c4499e8a4c5" } } ], "extra": [ 1, 116, 4, 38, 201, 201, 164, 172, 240, 73, 134, 62, 39, 249, 44, 5, 181, 69, 116, 211, 191, 184, 130, 177, 45, 63, 19, 183, 207, 34, 33, 222, 203, 2, 17, 0, 0, 0, 4, 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: