← previous blocknext block →recent activity
Analyzing
Block #105,870,346
9 transactions · 8 stateful · 2026-09-18 10:43:28 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,870,346 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e6a55ff…602e
0x34b655…2a6f
6 touches
3 conflicts
0x49299fcf…c552
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x9dccd2a9…2790
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
2 touches
0 conflicts
0xbb6e8844…f073
0x37db7f…ec7b
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
3 conflicts on slot 0x6e6a55ffbc…e8602e
Audit this contract →
← previous block·next block →recent activity