← previous blocknext block →recent activity
Analyzing
Block #87,759,085
19 transactions · 18 stateful · 2026-07-14 19:04:31 UTC
Parallelism
74/100
Blocked
28%
Avg conflicts / tx
0.37
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,759,085 · 19 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
6w07w18w010w112w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc204ea3…f1a3
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x2549dda6…9e24
0x34b655…2a6f
4 touches
1 conflict
0x323fde37…d7bb
0x34b655…2a6f
4 touches
1 conflict
0x323fde37…d7bc
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x36adf095…e10f
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 0xdc204ea323…a5f1a3
Audit this contract →
← previous block·next block →recent activity