← previous blocknext block →recent activity
Analyzing
Block #99,133,206
28 transactions · 23 stateful · 2026-08-25 20:03:33 UTC
Parallelism
86/100
Blocked
43%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,133,206 · 28 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
2w03w15w06w17w29w211w012w313w014w118w120w021w123w325w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc15631e2…8855
0x065c9d…c394
5 touches
3 conflicts
0x8f4e041c…01ae
0x34b655…2a6f
4 touches
1 conflict
0xb70727fa…3448
0x34b655…2a6f
4 touches
1 conflict
0xb7e8b0c4…dec3
0x34b655…2a6f
4 touches
1 conflict
0x997ccc40…4dfd
0x3bd359…433a
4 touches
1 conflict
0xe2745681…ff50
0x3bd359…433a
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity