← previous blocknext block →recent activity
Analyzing
Block #90,888,096
17 transactions · 16 stateful · 2026-07-27 22:14:05 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,888,096 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w19w211w312w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf18906a6…d2e3
0x34b655…2a6f
8 touches
6 conflicts
0x731f2745…9370
0xa6afd3…d132
6 touches
3 conflicts
0xb4cc9f41…b301
0x34b655…2a6f
6 touches
3 conflicts
0xbe54b7d5…1bda
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x8c674048…d0d6
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0xf18906a60b…97d2e3
Audit this contract →
← previous block·next block →recent activity