← previous blocknext block →recent activity
Analyzing
Block #107,814,384
24 transactions · 23 stateful · 2026-09-25 05:52:37 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,814,384 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w311w012w113w214w315w416w117w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf369641d…cd00
0x34b655…2a6f
14 touches
21 conflicts
0xba522812…1f1f
0x34b655…2a6f
14 touches
21 conflicts
0xdc16b418…2f5d
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xdbc6e634…e16c
0x1b6862…e19c
8 touches
6 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
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
21 conflicts on slot 0xf369641d57…d3cd00
Audit this contract →
← previous block·next block →recent activity