← previous blocknext block →recent activity
Analyzing
Block #87,614,437
14 transactions · 14 stateful · 2026-07-14 02:57:02 UTC
Parallelism
64/100
Blocked
29%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,614,437 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42341814…60f1
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x296e103c…993f
0x34b655…2a6f
4 touches
1 conflict
0x2b974671…5a68
0x34b655…2a6f
4 touches
1 conflict
0x68b75835…d6f3
0x34b655…2a6f
4 touches
1 conflict
0x76a1d783…e25e
0x34b655…2a6f
4 touches
1 conflict
0x789e5aad…ba83
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
6 conflicts on slot 0x423418147b…3460f1
Audit this contract →
← previous block·next block →recent activity