← previous blocknext block →recent activity
Analyzing
Block #87,411,102
22 transactions · 21 stateful · 2026-07-13 04:16:29 UTC
Parallelism
59/100
Blocked
38%
Avg conflicts / tx
1.41
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,411,102 · 22 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w212w313w414w515w616w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7c46fde6…d6a0
0x34b655…2a6f
6 touches
3 conflicts
0x6b22f8eb…68cb
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x8212e232…180e
0x34b655…2a6f
4 touches
1 conflict
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
28 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity