← previous blocknext block →recent activity
Analyzing
Block #105,435,070
17 transactions · 10 stateful · 2026-09-16 22:11:17 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,435,070 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00b6b37f…a0d8
0x34b655…2a6f
4 touches
1 conflict
0x03aa8633…a2d3
0x34b655…2a6f
4 touches
1 conflict
0x31519d10…f76b
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x440afa79…9614
0x34b655…2a6f
4 touches
1 conflict
0x56755b2b…8d44
0x34b655…2a6f
4 touches
1 conflict
0x57deed2f…23bb
0x34b655…2a6f
4 touches
1 conflict
0x5ce19b50…f20f
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
1 conflict on slot 0x00b6b37ff0…25a0d8
Audit this contract →
← previous block·next block →recent activity