← previous blocknext block →recent activity
Analyzing
Block #108,476,943
25 transactions · 23 stateful · 2026-09-27 13:27:13 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,476,943 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w012w013w114w219w321w122w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7efbf74f…f9d2
0x34b655…2a6f
8 touches
6 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
8 touches
6 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
6 touches
3 conflicts
0x5969523e…5191
0x34b655…2a6f
6 touches
3 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
6 touches
3 conflicts
0x7006165a…df17
0x34b655…2a6f
6 touches
3 conflicts
0x92f687cb…c1db
0x34b655…2a6f
6 touches
3 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x7efbf74f00…eef9d2
Audit this contract →
← previous block·next block →recent activity