← previous blocknext block →recent activity
Analyzing
Block #87,621,659
18 transactions · 18 stateful · 2026-07-14 03:45:18 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,621,659 · 18 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
2w03w16w07w110w011w112w213w314w415w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x640530ff…86bc
0x34b655…2a6f
6 touches
3 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
6 touches
3 conflicts
0xf940480b…baed
0x34b655…2a6f
6 touches
3 conflicts
0xfcc19724…4e34
0x34b655…2a6f
6 touches
3 conflicts
0x453f53a8…e541
0x34b655…2a6f
4 touches
1 conflict
0x4a6982a4…158c
0x34b655…2a6f
4 touches
1 conflict
0x6e96ad16…7991
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x640530ff6c…0186bc
Audit this contract →
← previous block·next block →recent activity