← previous blocknext block →recent activity
Analyzing
Block #98,335,237
16 transactions · 13 stateful · 2026-08-23 00:25:38 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,335,237 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w19w210w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9210e826…1414
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x68e5627d…6f8f
0x34b655…2a6f
6 touches
3 conflicts
0x6d787177…e955
0x34b655…2a6f
5 touches
3 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
4 touches
1 conflict
0x82a21578…a099
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0x9210e826c8…c41414
Audit this contract →
← previous block·next block →recent activity