← previous blocknext block →recent activity
Analyzing
Block #106,947,007
20 transactions · 19 stateful · 2026-09-22 05:04:20 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,947,007 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w111w212w214w315w416w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd7aed97…edad
0x34b655…2a6f
10 touches
10 conflicts
0x8590b692…b267
0x34b655…2a6f
6 touches
3 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7d764242…46b0
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0xe0a0c984…1a73
0x34b655…2a6f
4 touches
1 conflict
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 0xcd7aed97d2…ecedad
Audit this contract →
← previous block·next block →recent activity