← previous blocknext block →recent activity
Analyzing
Block #101,956,098
21 transactions · 19 stateful · 2026-09-04 17:09:18 UTC
Parallelism
71/100
Blocked
37%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,956,098 · 21 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
2w03w17w19w210w011w113w017w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4cf31a32…56e7
0x34b655…2a6f
6 touches
3 conflicts
0x3b096cfe…41e7
0x34b655…2a6f
4 touches
1 conflict
0x45082691…dff7
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x84d973b9…815f
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity