← previous blocknext block →recent activity
Analyzing
Block #87,704,955
30 transactions · 23 stateful · 2026-07-14 13:02:15 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,704,955 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w115w216w017w120w021w122w224w126w328w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42dd9d36…3fc0
0x34b655…2a6f
6 touches
3 conflicts
0xa4e3b3b1…0911
0x2a68ba…90c5
6 touches
3 conflicts
0x84290874…e04b
0xa6afd3…d132
5 touches
3 conflicts
0x02270397…bb9a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x9885a25f…292a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
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
3 conflicts on slot 0x42dd9d362d…df3fc0
Audit this contract →
← previous block·next block →recent activity