← previous blocknext block →recent activity
Analyzing
Block #87,587,701
21 transactions · 17 stateful · 2026-07-13 23:58:13 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,587,701 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w17w08w29w312w013w114w215w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x640530ff…86bc
0x34b655…2a6f
8 touches
6 conflicts
0xd644504a…1055
0x34b655…2a6f
8 touches
6 conflicts
0xc8fec9ca…2d60
0x34b655…2a6f
8 touches
6 conflicts
0xde1eb9a6…35cc
0x34b655…2a6f
8 touches
6 conflicts
0x9863393c…ce7b
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity