← previous blocknext block →recent activity
Analyzing
Block #105,852,644
24 transactions · 23 stateful · 2026-09-18 09:14:22 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,852,644 · 24 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
1w02w13w25w010w113w214w315w416w517w018w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x831f75b4…945d
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x2521fcb3…3eac
0x34b655…2a6f
8 touches
6 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
8 touches
6 conflicts
0xd79c9727…1233
0x34b655…2a6f
8 touches
6 conflicts
0xac09c31c…7d69
0x34b655…2a6f
8 touches
6 conflicts
0x46fc369e…d799
0xd32edf…ff58
5 touches
3 conflicts
0x1ab4ac1a…c2ec
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
15 conflicts on slot 0x831f75b4aa…17945d
Audit this contract →
← previous block·next block →recent activity