← previous blocknext block →recent activity
Analyzing
Block #107,978,816
32 transactions · 31 stateful · 2026-09-25 19:40:22 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,978,816 · 32 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
2w03w111w212w313w114w315w418w530w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
8 touches
6 conflicts
0x8a6f3950…a7cb
0xd32edf…ff58
7 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x471711ec…240a
0x34b655…2a6f
6 touches
3 conflicts
0x4d205b22…b005
0x34b655…2a6f
6 touches
3 conflicts
0xf2a6a8a3…eb7e
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity