← previous blocknext block →recent activity
Analyzing
Block #107,815,956
18 transactions · 17 stateful · 2026-09-25 06:00:32 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,815,956 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w010w111w212w213w316w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3fbb411a…fc32
0x34b655…2a6f
6 touches
3 conflicts
0xe23db711…61fd
0x34b655…2a6f
6 touches
3 conflicts
0xa23b9051…392f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x0a85a226…83c1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
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
3 conflicts on slot 0x3fbb411aaa…ecfc32
Audit this contract →
← previous block·next block →recent activity