← previous blocknext block →recent activity
Analyzing
Block #99,976,321
21 transactions · 18 stateful · 2026-08-28 19:01:06 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,976,321 · 21 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
1w03w05w16w17w211w012w113w014w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb14d7f1…e509
0x34b655…2a6f
6 touches
3 conflicts
0x2d3930d3…c9b8
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x5da59c2b…d7b2
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 0xfb14d7f18a…44e509
Audit this contract →
← previous block·next block →recent activity