← previous blocknext block →recent activity
Analyzing
Block #100,787,586
15 transactions · 14 stateful · 2026-08-31 15:07:28 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,787,586 · 15 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
6w07w18w29w310w413w514w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8311570f…5321
0x34b655…2a6f
10 touches
10 conflicts
0xfe4343d8…c25e
0x34b655…2a6f
10 touches
10 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x04ce368a…f721
0x34b655…2a6f
6 touches
3 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
6 touches
3 conflicts
0xf984d8ab…6e4f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
10 conflicts on slot 0x8311570feb…ae5321
Audit this contract →
← previous block·next block →recent activity