← previous blocknext block →recent activity
Analyzing
Block #87,735,502
21 transactions · 21 stateful · 2026-07-14 16:26:47 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,735,502 · 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
1w02w14w06w07w18w211w113w214w315w116w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7734fae8…226e
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
4 touches
1 conflict
0x26050074…6967
0x34b655…2a6f
4 touches
1 conflict
0x33d170e2…2c61
0x34b655…2a6f
4 touches
1 conflict
0x33d170e2…2c62
0x34b655…2a6f
4 touches
1 conflict
0x46e3da6b…72ca
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 0x7734fae853…69226e
Audit this contract →
← previous block·next block →recent activity