← previous blocknext block →recent activity
Analyzing
Block #88,360,014
33 transactions · 24 stateful · 2026-07-17 14:04:58 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,360,014 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w07w111w215w016w117w218w319w420w122w527w128w631w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x29c1a140…099f
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x71cbd5f6…e66e
0x34b655…2a6f
4 touches
1 conflict
0x745a7fd6…5fea
0x34b655…2a6f
4 touches
1 conflict
0x777ad666…1a52
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity