← previous blocknext block →recent activity
Analyzing
Block #105,682,995
25 transactions · 21 stateful · 2026-09-17 18:59:08 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,682,995 · 25 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
5w07w08w19w010w113w115w217w320w421w523w024w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88e92ec7…696d
0x34b655…2a6f
10 touches
10 conflicts
0xca613f5c…df23
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
6 touches
3 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
10 conflicts on slot 0x88e92ec750…6f696d
Audit this contract →
← previous block·next block →recent activity