← previous blocknext block →recent activity
Analyzing
Block #98,327,580
23 transactions · 20 stateful · 2026-08-22 23:47:07 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,327,580 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w110w011w012w113w214w315w416w517w618w719w221w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0036
0x35a73b…6042
16 touches
28 conflicts
0xfda39b6f…d4cc
0x754704…b603
16 touches
28 conflicts
0xaf831072…51dc
0x69a5f9…2fef
16 touches
28 conflicts
0x2ef1d89b…196d
0x754704…b603
16 touches
28 conflicts
0xaf831072…51d5
0x69a5f9…2fef
16 touches
28 conflicts
0xaf831072…51d6
0x69a5f9…2fef
16 touches
28 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
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: 0x35a73bac…1d6042
28 conflicts on slot 0x0000000000…000036
Audit this contract →
← previous block·next block →recent activity