← previous blocknext block →recent activity
Analyzing
Block #87,735,718
13 transactions · 12 stateful · 2026-07-14 16:28:13 UTC
Parallelism
54/100
Blocked
42%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,735,718 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
4 touches
1 conflict
0xbf0e051a…10a0
0x34b655…2a6f
4 touches
1 conflict
0xbf768a2f…f453
0x34b655…2a6f
4 touches
1 conflict
0xddc5edd9…899e
0x34b655…2a6f
4 touches
1 conflict
0xf5878c47…8d8e
0x34b655…2a6f
4 touches
1 conflict
0x2d7ea048…d78e
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity