← previous blocknext block →recent activity
Analyzing
Block #105,627,127
31 transactions · 25 stateful · 2026-09-17 14:17:54 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,627,127 · 31 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
1w02w13w25w39w010w111w012w013w114w018w121w125w226w327w328w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0d2c160…e188
0x34b655…2a6f
8 touches
6 conflicts
0xddf15bfc…09c0
0x34b655…2a6f
8 touches
6 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
8 touches
6 conflicts
0x6771eae2…7014
0x34b655…2a6f
8 touches
6 conflicts
0x678143da…dc6b
0x34b655…2a6f
8 touches
6 conflicts
0x01cd3f77…7099
0xd32edf…ff58
7 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
6 touches
3 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 0xb0d2c160ab…d1e188
Audit this contract →
← previous block·next block →recent activity