← previous blocknext block →recent activity
Analyzing
Block #87,616,438
21 transactions · 18 stateful · 2026-07-14 03:10:25 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,616,438 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w18w29w310w313w217w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6c566e1…a6fa
0x34b655…2a6f
10 touches
10 conflicts
0x745952b2…d90c
0x34b655…2a6f
8 touches
6 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x69ce640b…884a
0x34b655…2a6f
6 touches
3 conflicts
0xbad37226…3c86
0x34b655…2a6f
6 touches
3 conflicts
0x2a75708a…52ff
0xd32edf…ff58
5 touches
3 conflicts
0x0376dd2e…48ad
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
10 conflicts on slot 0xc6c566e196…62a6fa
Audit this contract →
← previous block·next block →recent activity