← previous blocknext block →recent activity
Analyzing
Block #106,555,931
26 transactions · 24 stateful · 2026-09-20 20:15:00 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,555,931 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w18w210w311w212w316w217w018w419w120w523w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd20e39…d524
0x34b655…2a6f
10 touches
10 conflicts
0xfadc118d…5d64
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x5a541bec…80fc
0x34b655…2a6f
6 touches
3 conflicts
0x5f13dc38…5584
0x34b655…2a6f
6 touches
3 conflicts
0xc86c4243…15f8
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
10 conflicts on slot 0xddd20e3989…a2d524
Audit this contract →
← previous block·next block →recent activity