← previous blocknext block →recent activity
Analyzing
Block #87,664,366
16 transactions · 14 stateful · 2026-07-14 08:30:44 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,664,366 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w29w010w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x2b661ce1…1881
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xde696e46…6446
0x34b655…2a6f
6 touches
3 conflicts
0xa37d59c6…996b
0x34b655…2a6f
6 touches
3 conflicts
0x56d52cc8…aea8
0x34b655…2a6f
4 touches
1 conflict
0x683604a1…4c1d
0x34b655…2a6f
4 touches
1 conflict
0x68c6b2fa…098d
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity