← previous blocknext block →recent activity
Analyzing
Block #100,023,631
22 transactions · 22 stateful · 2026-08-28 22:59:20 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,023,631 · 22 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
3w07w08w111w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb482658a…e4f5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
0x70cc08da…7ef7
0x34b655…2a6f
4 touches
1 conflict
0x5037e761…ba87
0x34b655…2a6f
4 touches
1 conflict
0x2999ebda…ce6c
0x34b655…2a6f
2 touches
0 conflicts
0x53043411…237a
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 0xb482658a15…f3e4f5
Audit this contract →
← previous block·next block →recent activity