← previous blocknext block →recent activity
Analyzing
Block #87,707,117
16 transactions · 16 stateful · 2026-07-14 13:16:44 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,707,117 · 16 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
1w04w05w18w29w310w311w113w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22c2bb0c…9d5d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc377ea03…e7cf
0x34b655…2a6f
4 touches
1 conflict
0xc5031114…58ac
0x34b655…2a6f
4 touches
1 conflict
0xd3a5c8e3…51f3
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1f8fad87…0106
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 0x22c2bb0c81…2b9d5d
Audit this contract →
← previous block·next block →recent activity