← previous blocknext block →recent activity
Analyzing
Block #106,551,956
23 transactions · 23 stateful · 2026-09-20 19:54:59 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,551,956 · 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
1w06w08w19w210w311w412w516w120w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13b1cd5c…28bc
0x34b655…2a6f
8 touches
6 conflicts
0x997ae611…3591
0x34b655…2a6f
8 touches
6 conflicts
0x0fc536fb…1aa1
0x34b655…2a6f
8 touches
6 conflicts
0x70986451…c6bd
0x34b655…2a6f
8 touches
6 conflicts
0x86cea35b…bdff
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x8590b692…b267
0x34b655…2a6f
6 touches
3 conflicts
0x35c96674…ccb7
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
6 conflicts on slot 0x13b1cd5c37…a328bc
Audit this contract →
← previous block·next block →recent activity