← previous blocknext block →recent activity
Analyzing
Block #87,294,433
29 transactions · 25 stateful · 2026-07-12 15:16:13 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,294,433 · 29 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w07w18w19w010w111w212w315w016w317w419w124w525w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xada5ad75…1d24
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
6 touches
3 conflicts
0xcff3aa14…c16c
0xd32edf…ff58
5 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x7523ad90…2ba5
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 0xada5ad75a3…de1d24
Audit this contract →
← previous block·next block →recent activity