← previous blocknext block →recent activity
Analyzing
Block #98,288,443
16 transactions · 14 stateful · 2026-08-22 20:30:09 UTC
Parallelism
63/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,288,443 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w19w210w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x742436a7…c4d4
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
0x34b655…2a6f
6 touches
3 conflicts
0xa074694c…7c34
0x34b655…2a6f
6 touches
3 conflicts
0xbceecf11…0120
0x34b655…2a6f
6 touches
3 conflicts
0x5ee07d61…5328
0x34b655…2a6f
4 touches
1 conflict
0x80884f59…ac94
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 0xc824469a90…af641f
Audit this contract →
← previous block·next block →recent activity