← previous blocknext block →recent activity
Analyzing
Block #87,581,084
14 transactions · 14 stateful · 2026-07-13 23:13:59 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,581,084 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41bc5f7b…26f2
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xb1c67a7d…b9b1
0x34b655…2a6f
4 touches
1 conflict
0xcf9fbcb0…563a
0x34b655…2a6f
4 touches
1 conflict
0xdcd47ab6…d8f9
0x34b655…2a6f
4 touches
1 conflict
0xe935257b…817f
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
1 conflict on slot 0x41bc5f7b12…9826f2
Audit this contract →
← previous block·next block →recent activity