← previous blocknext block →recent activity
Analyzing
Block #99,200,543
30 transactions · 28 stateful · 2026-08-26 01:42:19 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
1.5
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,200,543 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w416w517w618w720w822w324w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x11258774…9892
0x2a68ba…90c5
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x631b4113…baa9
0x34b655…2a6f
8 touches
6 conflicts
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xaa58d20f…6125
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
10 conflicts on slot 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity