← previous blocknext block →recent activity
Analyzing
Block #87,593,071
20 transactions · 16 stateful · 2026-07-14 00:34:09 UTC
Parallelism
70/100
Blocked
31%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,593,071 · 20 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
3w04w15w29w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
10 touches
10 conflicts
0x34d95d94…3a16
0x34b655…2a6f
6 touches
3 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
6 touches
3 conflicts
0x6c0d4c60…31c4
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x167de262…f61f
0x34b655…2a6f
6 touches
3 conflicts
0x2fade833…5de4
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity