← previous blocknext block →recent activity
Analyzing
Block #87,046,296
9 transactions · 7 stateful · 2026-07-11 11:37:03 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,046,296 · 9 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb277c58…e388
0x34b655…2a6f
4 touches
1 conflict
0x0ae9d2df…f788
0x34b655…2a6f
4 touches
1 conflict
0x0ae9d2df…f787
0x34b655…2a6f
4 touches
1 conflict
0xb71f11fc…e362
0x34b655…2a6f
4 touches
1 conflict
0x685376b7…a209
0x34b655…2a6f
3 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
2 touches
0 conflicts
0x508bbf1b…fe95
0x34b655…2a6f
2 touches
0 conflicts
0x519d580e…709c
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 0xbb277c5800…bce388
Audit this contract →
← previous block·next block →recent activity