← previous blocknext block →recent activity
Analyzing
Block #87,594,308
10 transactions · 8 stateful · 2026-07-14 00:42:25 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,594,308 · 10 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
4w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd42fdceb…d869
0x34b655…2a6f
4 touches
1 conflict
0xd42fdceb…d86a
0x34b655…2a6f
4 touches
1 conflict
0xea0fee48…1fab
0x34b655…2a6f
4 touches
1 conflict
0x0b844a5a…3ee4
0x34b655…2a6f
3 touches
1 conflict
0x01c969a3…227b
0x34b655…2a6f
2 touches
0 conflicts
0x0a5dbc1e…74cc
0x34b655…2a6f
2 touches
0 conflicts
0x12a92ce8…db54
0x34b655…2a6f
2 touches
0 conflicts
0x176771f9…c1a4
0x34b655…2a6f
2 touches
0 conflicts
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 0xd42fdceb99…57d869
Audit this contract →
← previous block·next block →recent activity