← previous blocknext block →recent activity
Analyzing
Block #106,543,343
23 transactions · 22 stateful · 2026-09-20 19:11:39 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,543,343 · 23 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
1w02w13w24w05w16w27w38w49w511w014w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x735a86cd…b64d
0x34b655…2a6f
14 touches
21 conflicts
0x8ec0395a…d7ba
0x34b655…2a6f
12 touches
15 conflicts
0x4be9812b…48a9
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xd6071d1d…496b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x12df64a4…0233
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
21 conflicts on slot 0x735a86cd19…53b64d
Audit this contract →
← previous block·next block →recent activity