← previous blocknext block →recent activity
Analyzing
Block #87,704,130
25 transactions · 24 stateful · 2026-07-14 12:56:44 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,704,130 · 25 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
1w02w13w24w010w011w114w015w116w219w320w121w223w024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb36b8448…9a06
0x34b655…2a6f
8 touches
6 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd7d3e7dd…2bf3
0x34b655…2a6f
6 touches
3 conflicts
0x7a916b05…8a00
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x410b84ab…1dbc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0xb36b844891…269a06
Audit this contract →
← previous block·next block →recent activity