← previous blocknext block →recent activity
Analyzing
Block #108,619,882
13 transactions · 11 stateful · 2026-09-28 01:26:59 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,619,882 · 13 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
5w07w08w19w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ff9db2e…22f6
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xd7fbd4e9…61ff
0x34b655…2a6f
4 touches
1 conflict
0xf359b0f1…b99d
0x34b655…2a6f
4 touches
1 conflict
0x0215d8e5…68d5
0x34b655…2a6f
2 touches
0 conflicts
0x0d8a97d7…b5d8
0x34b655…2a6f
2 touches
0 conflicts
0x1393df1d…afbd
0x34b655…2a6f
2 touches
0 conflicts
0x305b3aa7…527a
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 0x3ff9db2e2d…9122f6
Audit this contract →
← previous block·next block →recent activity