← previous blocknext block →recent activity
Analyzing
Block #107,817,033
25 transactions · 20 stateful · 2026-09-25 06:05:57 UTC
Parallelism
76/100
Blocked
55%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,817,033 · 25 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
1w02w13w24w39w010w111w212w313w414w515w019w020w123w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xab0c9ca9…926b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xb0e4f69d…34e8
0x1b6862…e19c
8 touches
6 conflicts
0x00e96ac5…8e2c
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
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
15 conflicts on slot 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity