← previous blocknext block →recent activity
Analyzing
Block #87,329,010
30 transactions · 28 stateful · 2026-07-12 19:07:24 UTC
Parallelism
77/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,329,010 · 30 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
1w02w15w08w09w110w211w312w415w116w217w319w426w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x567bb003…113a
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x9f287382…28e5
0x34b655…2a6f
8 touches
6 conflicts
0xc0124edf…7d30
0x34b655…2a6f
8 touches
6 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
6 touches
3 conflicts
0x63b15849…80b2
0x34b655…2a6f
6 touches
3 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 0x567bb0034c…9f113a
Audit this contract →
← previous block·next block →recent activity