← previous blocknext block →recent activity
Analyzing
Block #87,048,784
11 transactions · 11 stateful · 2026-07-11 11:53:38 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,048,784 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w16w27w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa248a5dd…4a69
0x34b655…2a6f
6 touches
3 conflicts
0xce3de73c…ae36
0x34b655…2a6f
4 touches
1 conflict
0xe20c87ea…7680
0x34b655…2a6f
4 touches
1 conflict
0x0ea46b1d…c9a4
0x34b655…2a6f
4 touches
1 conflict
0x53c922c1…1f78
0x34b655…2a6f
4 touches
1 conflict
0x777c0352…4d8c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xb104db11…2208
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 0xa248a5dd13…914a69
Audit this contract →
← previous block·next block →recent activity