← previous blocknext block →recent activity
Analyzing
Block #87,409,465
14 transactions · 13 stateful · 2026-07-13 04:05:28 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,409,465 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w09w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05975727…7fcf
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4fdbc928…4a1f
0x34b655…2a6f
4 touches
1 conflict
0x4fdbc928…4a20
0x34b655…2a6f
4 touches
1 conflict
0x64312ffa…cdfa
0x34b655…2a6f
4 touches
1 conflict
0x69ce640b…884a
0x34b655…2a6f
4 touches
1 conflict
0x7d6e48e8…f2b5
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 0x05975727b0…467fcf
Audit this contract →
← previous block·next block →recent activity