← previous blocknext block →recent activity
Analyzing
Block #87,418,475
34 transactions · 32 stateful · 2026-07-13 05:05:46 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.62
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,418,475 · 34 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
2w03w14w25w06w17w08w19w010w111w112w213w314w415w516w417w518w620w721w130w831w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d56e62c…60d6
0x34b655…2a6f
10 touches
10 conflicts
0xf4af322a…5856
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xda46a376…f6a6
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 0x2d56e62cd5…8060d6
Audit this contract →
← previous block·next block →recent activity