← previous blocknext block →recent activity
Analyzing
Block #107,815,175
18 transactions · 18 stateful · 2026-09-25 05:56:36 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,815,175 · 18 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
1w02w13w24w38w09w110w211w312w413w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x6fd9ae7c…e984
0x1b6862…e19c
8 touches
6 conflicts
0x49ec87b8…8d61
0xd32edf…ff58
7 touches
6 conflicts
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0x09a43d55…7c20
0x34b655…2a6f
6 touches
3 conflicts
0x740fff9f…4244
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
10 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity