← previous blocknext block →recent activity
Analyzing
Block #87,629,173
23 transactions · 21 stateful · 2026-07-14 04:35:36 UTC
Parallelism
70/100
Blocked
57%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,629,173 · 23 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
1w02w13w25w06w17w18w210w312w313w414w516w317w622w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96efe05d…5d48
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x973729b4…d3fb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x50115415…f935
0x34b655…2a6f
6 touches
3 conflicts
0x63f8a50d…333b
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 0x96efe05d27…da5d48
Audit this contract →
← previous block·next block →recent activity