← previous blocknext block →recent activity
Analyzing
Block #105,683,245
28 transactions · 27 stateful · 2026-09-17 19:00:23 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,683,245 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w012w113w214w320w026w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9af9157…5a6e
0x34b655…2a6f
8 touches
6 conflicts
0xf48fa71e…bb52
0x34b655…2a6f
8 touches
6 conflicts
0xb4c3caee…2ca2
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x8ed2a645…b3ce
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0xa9af9157e5…cc5a6e
Audit this contract →
← previous block·next block →recent activity