← previous blocknext block →recent activity
Analyzing
Block #106,040,286
11 transactions · 10 stateful · 2026-09-19 00:59:48 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,040,286 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xb9a0dde5…9e2b
0x34b655…2a6f
4 touches
1 conflict
0xefaeef6e…0729
0xd32edf…ff58
3 touches
1 conflict
0x0145aa28…106b
0x34b655…2a6f
2 touches
0 conflicts
0x1a3fddfb…a5ee
0x34b655…2a6f
2 touches
0 conflicts
0x2249932e…474a
0x34b655…2a6f
2 touches
0 conflicts
0x25fd5528…ff50
0x34b655…2a6f
2 touches
0 conflicts
0x458113a8…a1fe
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity