← previous blocknext block →recent activity
Analyzing
Block #87,306,786
20 transactions · 19 stateful · 2026-07-12 16:38:45 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,306,786 · 20 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
1w02w13w24w07w010w111w213w114w015w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc88f593e…5d93
0x336ed4…c59c
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb6135f02…1046
0x34b655…2a6f
4 touches
1 conflict
0xc561f84c…527c
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: 0x336ed437…cfc59c
3 conflicts on slot 0xc88f593e3b…e65d93
Audit this contract →
← previous block·next block →recent activity