← previous blocknext block →recent activity
Analyzing
Block #87,587,509
15 transactions · 14 stateful · 2026-07-13 23:56:56 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,587,509 · 15 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
1w02w16w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x212c5b04…5f01
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x1c9f10fd…ecb0
0x34b655…2a6f
4 touches
1 conflict
0x1f2cd70b…94be
0x34b655…2a6f
4 touches
1 conflict
0x206fb8db…a146
0x34b655…2a6f
4 touches
1 conflict
0x27bfe98b…2053
0x34b655…2a6f
4 touches
1 conflict
0x344bc09a…942f
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 0x212c5b0431…f85f01
Audit this contract →
← previous block·next block →recent activity