← previous blocknext block →recent activity
Analyzing
Block #105,582,780
24 transactions · 20 stateful · 2026-09-17 10:34:38 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,582,780 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w09w114w216w317w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42900ee6…dfd3
0x34b655…2a6f
14 touches
21 conflicts
0x1e737223…2278
0x34b655…2a6f
12 touches
15 conflicts
0x2d3930d3…c9b8
0x34b655…2a6f
8 touches
6 conflicts
0xcadd9a74…8bb7
0x34b655…2a6f
6 touches
3 conflicts
0x7b42f6a7…f49c
0x34b655…2a6f
6 touches
3 conflicts
0x59f5bb3d…0bc5
0x34b655…2a6f
4 touches
1 conflict
0x7daf6443…fd36
0x34b655…2a6f
4 touches
1 conflict
0x898a08aa…c855
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
21 conflicts on slot 0x42900ee6cf…a1dfd3
Audit this contract →
← previous block·next block →recent activity