← previous blocknext block →recent activity
Analyzing
Block #100,787,676
23 transactions · 22 stateful · 2026-08-31 15:07:55 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,787,676 · 23 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
1w04w05w19w111w212w313w318w021w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69ee34d1…30f8
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x31315dde…9465
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x6bf71f68…fd07
0x34b655…2a6f
4 touches
1 conflict
0xb3aa2022…9e09
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 0x69ee34d107…a730f8
Audit this contract →
← previous block·next block →recent activity