← previous blocknext block →recent activity
Analyzing
Block #87,616,538
18 transactions · 13 stateful · 2026-07-14 03:11:05 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,616,538 · 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
2w03w16w07w110w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e970d38…d1c4
0x34b655…2a6f
8 touches
6 conflicts
0x69ce640b…884a
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x10ef891f…d725
0x34b655…2a6f
4 touches
1 conflict
0x10ef891f…d726
0x34b655…2a6f
4 touches
1 conflict
0x149e9cbf…e903
0x34b655…2a6f
4 touches
1 conflict
0x14c5407b…4a40
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x4e970d38f3…11d1c4
Audit this contract →
← previous block·next block →recent activity