← previous blocknext block →recent activity
Analyzing
Block #99,114,143
12 transactions · 11 stateful · 2026-08-25 18:27:32 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,114,143 · 12 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
2w05w06w18w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xb2d8af24…4750
0x34b655…2a6f
4 touches
1 conflict
0x024582ce…e73c
0x34b655…2a6f
2 touches
0 conflicts
0x062fa9cf…b1f1
0x34b655…2a6f
2 touches
0 conflicts
0x3939bebf…6270
0x34b655…2a6f
2 touches
0 conflicts
0x46e2bb67…d8b3
0x34b655…2a6f
2 touches
0 conflicts
0x5c0f61f5…6909
0x34b655…2a6f
2 touches
0 conflicts
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 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity