← previous blocknext block →recent activity
Analyzing
Block #87,512,761
20 transactions · 19 stateful · 2026-07-13 15:36:19 UTC
Parallelism
70/100
Blocked
26%
Avg conflicts / tx
0.4
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,512,761 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w09w110w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbedfd60…0fec
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1191dbf7…8e85
0x34b655…2a6f
4 touches
1 conflict
0x13c5b486…d41e
0x34b655…2a6f
4 touches
1 conflict
0x20492d53…80f9
0x34b655…2a6f
4 touches
1 conflict
0x39bd1fab…a39c
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
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 0xbbedfd6094…580fec
Audit this contract →
← previous block·next block →recent activity