← previous blocknext block →recent activity
Analyzing
Block #118,417,235
14 transactions · 11 stateful · 2026-11-01 08:01:59 UTC
Parallelism
86/100
Blocked
9%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #118,417,235 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46c14e01…ff09
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xaf54cdd0…405c
0x34b655…2a6f
3 touches
1 conflict
0x09aff580…d5a1
0x34b655…2a6f
3 touches
1 conflict
0x0ccd739a…9ab8
0x34b655…2a6f
3 touches
1 conflict
0x3d0ade64…777e
0x34b655…2a6f
3 touches
1 conflict
0x2fde3e82…2035
0x34b655…2a6f
2 touches
0 conflicts
0x3a4f9794…d7b3
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
1 conflict on slot 0x46c14e01c8…d5ff09
Audit this contract →
← previous block·next block →recent activity