← previous blocknext block →recent activity
Analyzing
Block #87,418,214
30 transactions · 27 stateful · 2026-07-13 05:04:02 UTC
Parallelism
63/100
Blocked
59%
Avg conflicts / tx
2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,418,214 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w08w19w210w311w412w516w320w723w126w827w928w1029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc514314c…1aa4
0x34b655…2a6f
14 touches
21 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x7c63ea28…e8af
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0xca2926e0…61b5
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
21 conflicts on slot 0xc514314ca6…fa1aa4
Audit this contract →
← previous block·next block →recent activity