← previous blocknext block →recent activity
Analyzing
Block #108,103,581
26 transactions · 24 stateful · 2026-09-26 06:08:11 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,103,581 · 26 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
4w07w09w010w011w112w014w216w317w418w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4451bf51…8dde
0x34b655…2a6f
8 touches
6 conflicts
0x30f54ecb…ab9a
0x34b655…2a6f
8 touches
6 conflicts
0x939cdd56…00c8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6b22b4c6…fecb
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1f103912…aca3
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x4451bf5197…f18dde
Audit this contract →
← previous block·next block →recent activity