← previous blocknext block →recent activity
Analyzing
Block #87,591,382
24 transactions · 20 stateful · 2026-07-14 00:22:50 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,591,382 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w312w413w515w118w621w022w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc8fec9ca…2d60
0x34b655…2a6f
6 touches
3 conflicts
0x0ee13be7…7b2c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x1f40ac22…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x17cc5ec3…ae0e
0x34b655…2a6f
6 touches
3 conflicts
0xb1c67a7d…b9b1
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity