← previous blocknext block →recent activity
Analyzing
Block #107,816,508
32 transactions · 25 stateful · 2026-09-25 06:03:18 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.28
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #107,816,508 · 32 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w012w013w114w215w316w417w518w619w720w821w923w131w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xbdd97c21…e3d0
0x34b655…2a6f
10 touches
10 conflicts
0x4cd7fdf4…7197
0x34b655…2a6f
10 touches
10 conflicts
0x5cf4d55d…c588
0x34b655…2a6f
10 touches
10 conflicts
0xcb2df07b…732d
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xac79a0c7…be16
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
15 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity