← previous blocknext block →recent activity
Analyzing
Block #87,050,085
21 transactions · 20 stateful · 2026-07-11 12:02:19 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,050,085 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w413w014w515w619w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63c900f4…2600
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
10 touches
10 conflicts
0x97c67486…27fe
0x34b655…2a6f
10 touches
10 conflicts
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0x53c922c1…1f78
0x34b655…2a6f
10 touches
10 conflicts
0x7ae63663…9d94
0x34b655…2a6f
8 touches
6 conflicts
0x9aba2989…44a5
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x63c900f479…962600
Audit this contract →
← previous block·next block →recent activity