← previous blocknext block →recent activity
Analyzing
Block #87,362,116
27 transactions · 24 stateful · 2026-07-12 22:48:45 UTC
Parallelism
78/100
Blocked
63%
Avg conflicts / tx
1.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,362,116 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w47w48w59w012w013w114w215w316w123w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x851145…3f07
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xf15f80b2…4254
0x851145…3f07
10 touches
10 conflicts
0x3b115d7b…33ac
0x2a68ba…90c5
10 touches
10 conflicts
0x8ab4527c…3788
0xd32edf…ff58
9 touches
10 conflicts
0x0fde64da…aa3e
0x2a68ba…90c5
8 touches
6 conflicts
0x7a12283f…b18a
0x69df8a…6292
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity