← previous blocknext block →recent activity
Analyzing
Block #105,377,232
15 transactions · 15 stateful · 2026-09-16 17:20:05 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,377,232 · 15 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
2w04w05w19w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10cc9469…5b6c
0x34b655…2a6f
8 touches
6 conflicts
0x18978822…2623
0x34b655…2a6f
6 touches
3 conflicts
0x54d4d3b9…b7ed
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc40c1915…55ed
0x34b655…2a6f
4 touches
1 conflict
0x1f396cee…862f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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 0x10cc9469c0…115b6c
Audit this contract →
← previous block·next block →recent activity