← previous blocknext block →recent activity
Analyzing
Block #87,694,898
17 transactions · 17 stateful · 2026-07-14 11:54:45 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,694,898 · 17 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
1w03w19w210w314w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62222abd…e410
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe2307994…acad
0x34b655…2a6f
4 touches
1 conflict
0x2f358e74…1022
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x676b7ed0…a255
0x34b655…2a6f
4 touches
1 conflict
0xa4e88c04…603d
0x34b655…2a6f
4 touches
1 conflict
0xb95e925b…392d
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
3 conflicts on slot 0x62222abdea…6fe410
Audit this contract →
← previous block·next block →recent activity