← previous blocknext block →recent activity
Analyzing
Block #108,961,363
24 transactions · 22 stateful · 2026-09-29 06:10:09 UTC
Parallelism
75/100
Blocked
55%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,961,363 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w49w111w515w117w218w319w422w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x380778a9…6cf4
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x3a00de10…175c
0x34b655…2a6f
8 touches
6 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
6 touches
3 conflicts
0x72083f0d…082a
0x34b655…2a6f
6 touches
3 conflicts
0xf06fce24…887d
0x34b655…2a6f
6 touches
3 conflicts
0x0121c33f…8b6a
0x34b655…2a6f
4 touches
1 conflict
0x6235638c…643c
0x1b6862…e19c
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
6 conflicts on slot 0x380778a9da…096cf4
Audit this contract →
← previous block·next block →recent activity