← previous blocknext block →recent activity
Analyzing
Block #108,965,391
21 transactions · 20 stateful · 2026-09-29 06:30:40 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,965,391 · 21 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
3w04w15w06w17w28w311w413w216w318w019w120w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9868b52…c77f
0x34b655…2a6f
10 touches
10 conflicts
0x631b4113…baa9
0x34b655…2a6f
10 touches
10 conflicts
0x3a3c1ed9…9dd5
0x34b655…2a6f
8 touches
6 conflicts
0x48719cbe…5484
0x34b655…2a6f
8 touches
6 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
8 touches
6 conflicts
0x342fe47d…42ae
0x34b655…2a6f
8 touches
6 conflicts
0x2a8bc05a…0464
0x37db7f…ec7b
8 touches
6 conflicts
0xa93fef74…94b3
0x37db7f…ec7b
8 touches
6 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
10 conflicts on slot 0xb9868b5233…c6c77f
Audit this contract →
← previous block·next block →recent activity