← previous blocknext block →recent activity
Analyzing
Block #87,731,132
64 transactions · 41 stateful · 2026-07-14 15:57:33 UTC
Parallelism
78/100
Blocked
68%
Avg conflicts / tx
1.98
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,731,132 · 64 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w26w38w211w312w421w022w136w037w138w239w340w441w542w643w744w845w946w1047w1161w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
12 touches
15 conflicts
0x152a3ec6…42d7
0x34b655…2a6f
10 touches
10 conflicts
0x1ec7ada6…505b
0x34b655…2a6f
10 touches
10 conflicts
0x29856edf…841b
0x34b655…2a6f
10 touches
10 conflicts
0x3c550c68…de2c
0x34b655…2a6f
10 touches
10 conflicts
0x49f5a697…72c0
0x34b655…2a6f
10 touches
10 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
10 touches
10 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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity