← previous blocknext block →recent activity
Analyzing
Block #87,731,148
12 transactions · 11 stateful · 2026-07-14 15:57:39 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,731,148 · 12 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
1w02w15w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ab016af…dae9
0x34b655…2a6f
8 touches
6 conflicts
0xc6bb7e6c…bf35
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xa3d14dff…15d3
0x34b655…2a6f
4 touches
1 conflict
0xa3d14dff…15d4
0x34b655…2a6f
4 touches
1 conflict
0xac7fe43e…4c38
0x34b655…2a6f
4 touches
1 conflict
0xb176789b…c34b
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
6 conflicts on slot 0x7ab016afb2…a7dae9
Audit this contract →
← previous block·next block →recent activity