← previous blocknext block →recent activity
Analyzing
Block #106,956,481
16 transactions · 16 stateful · 2026-09-22 05:52:02 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,956,481 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w19w010w111w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
12 touches
15 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
10 touches
10 conflicts
0x5969523e…5191
0x34b655…2a6f
10 touches
10 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
10 touches
10 conflicts
0x7efbf74f…f9d2
0x34b655…2a6f
10 touches
10 conflicts
0x8714eb4d…e184
0x34b655…2a6f
10 touches
10 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
10 touches
10 conflicts
0xabfdfd0e…20bf
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity