← previous blocknext block →recent activity
Analyzing
Block #87,078,412
57 transactions · 15 stateful · 2026-07-11 15:11:18 UTC
Parallelism
93/100
Blocked
33%
Avg conflicts / tx
0.16
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,078,412 · 57 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
1w02w13w28w051w052w155w256w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e166a45…98a7
0x34b655…2a6f
6 touches
3 conflicts
0x03678446…9cfd
0xd32edf…ff58
5 touches
3 conflicts
0x4e5b9519…f1d9
0x34b655…2a6f
4 touches
1 conflict
0x9a964905…d410
0x34b655…2a6f
4 touches
1 conflict
0xc788862c…c259
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
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
3 conflicts on slot 0x1e166a4530…8298a7
Audit this contract →
← previous block·next block →recent activity