← previous blocknext block →recent activity
Analyzing
Block #101,969,720
16 transactions · 16 stateful · 2026-09-04 18:18:21 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,969,720 · 16 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
1w04w15w27w39w210w413w514w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b13e91…855d
0x34b655…2a6f
10 touches
10 conflicts
0x9ecf942d…fdb7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x2a565afa…37fc
0x34b655…2a6f
4 touches
1 conflict
0x99855f24…1573
0x34b655…2a6f
4 touches
1 conflict
0x3d408a46…8a53
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x91b13e914b…cb855d
Audit this contract →
← previous block·next block →recent activity