← previous blocknext block →recent activity
Analyzing
Block #99,984,232
18 transactions · 17 stateful · 2026-08-28 19:40:56 UTC
Parallelism
61/100
Blocked
35%
Avg conflicts / tx
0.78
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,984,232 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w07w18w210w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa11b60f7…8e8b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa5811d93…8c73
0x34b655…2a6f
6 touches
3 conflicts
0x5666db7d…5dc4
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f763…10b1
0x34b655…2a6f
6 touches
3 conflicts
0x6c28863e…840e
0x34b655…2a6f
4 touches
1 conflict
0x753b2da4…7a6d
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 0xa11b60f7c7…f88e8b
Audit this contract →
← previous block·next block →recent activity