← previous blocknext block →recent activity
Analyzing
Block #106,192,258
11 transactions · 11 stateful · 2026-09-19 13:44:37 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,192,258 · 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
1w04w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0x0033014e…086d
0x34b655…2a6f
4 touches
1 conflict
0x032ec3de…2902
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x1a89dc58…ddf9
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x786d66ce…ae70
0x34b655…2a6f
4 touches
1 conflict
0x92fa1dc0…b239
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
1 conflict on slot 0xecd87a399c…10d9c5
Audit this contract →
← previous block·next block →recent activity