← previous blocknext block →recent activity
Analyzing
Block #87,611,151
22 transactions · 21 stateful · 2026-07-14 02:35:03 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,611,151 · 22 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
1w02w04w05w16w27w38w49w513w114w115w216w119w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x0eeb2a30…6909
0x34b655…2a6f
8 touches
6 conflicts
0xd9642cf4…8856
0x34b655…2a6f
6 touches
3 conflicts
0x344bc09a…942f
0x34b655…2a6f
4 touches
1 conflict
0x57584a65…1454
0x34b655…2a6f
4 touches
1 conflict
0x656b2803…dc85
0x34b655…2a6f
4 touches
1 conflict
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x96c46b5c…c579
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity