← previous blocknext block →recent activity
Analyzing
Block #107,842,269
41 transactions · 35 stateful · 2026-09-25 08:12:58 UTC
Parallelism
81/100
Blocked
60%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,842,269 · 41 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
1w02w13w24w35w46w57w619w520w321w132w640w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
16 touches
28 conflicts
0x3942c79b…709f
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001f
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002f
0x1b6862…e19c
12 touches
15 conflicts
0x59658b83…222c
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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
28 conflicts on slot 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity