← previous blocknext block →recent activity
Analyzing
Block #98,382,071
16 transactions · 16 stateful · 2026-08-23 04:21:14 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,382,071 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w09w110w211w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x643e47e3…69f4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x17673a02…749e
0x34b655…2a6f
4 touches
1 conflict
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0x3f798539…99c4
0x34b655…2a6f
4 touches
1 conflict
0x544745e8…d72e
0x34b655…2a6f
4 touches
1 conflict
0x575a0a6a…a844
0x34b655…2a6f
4 touches
1 conflict
0x5c847277…8e6f
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 0x643e47e358…3d69f4
Audit this contract →
← previous block·next block →recent activity