← previous blocknext block →recent activity
Analyzing
Block #105,881,662
20 transactions · 16 stateful · 2026-09-18 11:40:25 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,881,662 · 20 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
1w04w15w213w314w415w519w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46c14e01…ff09
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4118bd12…924a
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x0f65f95e…37fc
0x34b655…2a6f
4 touches
1 conflict
0x0fb20484…1982
0x34b655…2a6f
2 touches
0 conflicts
0x1c836c34…924d
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
6 conflicts on slot 0x46c14e01c8…d5ff09
Audit this contract →
← previous block·next block →recent activity