← previous blocknext block →recent activity
Analyzing
Block #106,385,826
24 transactions · 23 stateful · 2026-09-20 05:58:51 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,385,826 · 24 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
1w02w06w19w110w212w115w216w217w318w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51d607f1…6458
0x34b655…2a6f
16 touches
28 conflicts
0x0463db49…5d05
0x34b655…2a6f
12 touches
15 conflicts
0xba33378a…f1df
0x34b655…2a6f
10 touches
10 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
8 touches
6 conflicts
0x74e46435…fdcd
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
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
28 conflicts on slot 0x51d607f1c3…a96458
Audit this contract →
← previous block·next block →recent activity