← previous blocknext block →recent activity
Analyzing
Block #87,593,745
15 transactions · 14 stateful · 2026-07-14 00:38:39 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,593,745 · 15 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
5w06w17w29w311w012w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1af
0x158622…375e
6 touches
3 conflicts
0x8a35acfb…d1ae
0x158622…375e
6 touches
3 conflicts
0x4bf3de8f…d4bb
0x158622…375e
4 touches
1 conflict
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d19b
0x158622…375e
4 touches
1 conflict
0x8a35acfb…d19c
0x158622…375e
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity