← previous blocknext block →recent activity
Analyzing
Block #106,924,116
36 transactions · 36 stateful · 2026-09-22 03:09:07 UTC
Parallelism
75/100
Blocked
72%
Avg conflicts / tx
2.28
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,924,116 · 36 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w626w128w329w431w335w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ec9ff52…e6f7
0x34b655…2a6f
14 touches
21 conflicts
0x40804728…91d5
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
12 touches
15 conflicts
0xd18a8dca…452e
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
21 conflicts on slot 0x4ec9ff52ce…67e6f7
Audit this contract →
← previous block·next block →recent activity