← previous blocknext block →recent activity
Analyzing
Block #100,027,135
17 transactions · 17 stateful · 2026-08-28 23:16:59 UTC
Parallelism
76/100
Blocked
24%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,027,135 · 17 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
1w06w07w18w29w010w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0x932a9590…0b19
0x34b655…2a6f
6 touches
3 conflicts
0x2c38ba12…d2e4
0x34b655…2a6f
6 touches
3 conflicts
0x639be938…49c4
0x34b655…2a6f
6 touches
3 conflicts
0xf72228f6…970c
0x34b655…2a6f
6 touches
3 conflicts
0x64e1f0ce…7159
0x1b6862…e19c
4 touches
1 conflict
0x24bb46f7…3853
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x69411fb3ba…bce36d
Audit this contract →
← previous block·next block →recent activity