← previous blocknext block →recent activity
Analyzing
Block #87,594,560
14 transactions · 12 stateful · 2026-07-14 00:44:06 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,594,560 · 14 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
1w02w15w06w19w210w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe197e523…ef9c
0x34b655…2a6f
6 touches
3 conflicts
0x48260180…a412
0x34b655…2a6f
4 touches
1 conflict
0x4947e67f…aa39
0x34b655…2a6f
4 touches
1 conflict
0x4947e67f…aa3a
0x34b655…2a6f
4 touches
1 conflict
0x62bd1793…0097
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity