← previous blocknext block →recent activity
Analyzing
Block #87,785,004
13 transactions · 13 stateful · 2026-07-14 21:57:57 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,785,004 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd50d8366…df9d
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xe8bae471…b4f4
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00893bb8…77ee
0x34b655…2a6f
4 touches
1 conflict
0x017e2d37…794f
0x34b655…2a6f
4 touches
1 conflict
0x17c73702…674c
0x34b655…2a6f
4 touches
1 conflict
0x666f54f8…873c
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
1 conflict on slot 0xd50d836695…72df9d
Audit this contract →
← previous block·next block →recent activity