← previous blocknext block →recent activity
Analyzing
Block #106,428,341
20 transactions · 19 stateful · 2026-09-20 09:32:48 UTC
Parallelism
55/100
Blocked
58%
Avg conflicts / tx
1.85
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,428,341 · 20 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
1w02w13w24w05w16w27w311w413w314w515w616w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6650a74…44b9
0x34b655…2a6f
16 touches
28 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
8 touches
6 conflicts
0x172b0de5…980b
0x34b655…2a6f
8 touches
6 conflicts
0xbc0d66ec…873c
0x34b655…2a6f
8 touches
6 conflicts
0xea2a1d1b…4115
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 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 0xf6650a7492…e644b9
Audit this contract →
← previous block·next block →recent activity