← previous blocknext block →recent activity
Analyzing
Block #106,373,636
23 transactions · 22 stateful · 2026-09-20 04:57:30 UTC
Parallelism
74/100
Blocked
55%
Avg conflicts / tx
1.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,373,636 · 23 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
1w02w13w24w35w06w17w28w09w110w212w319w420w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8d8e93…e68a
0x34b655…2a6f
10 touches
10 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
8 touches
6 conflicts
0xf54391cd…e33c
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
0x34b655…2a6f
6 touches
3 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x60a536a6…ef7a
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 0x5c8d8e93a8…c8e68a
Audit this contract →
← previous block·next block →recent activity