← previous blocknext block →recent activity
Analyzing
Block #87,705,080
32 transactions · 24 stateful · 2026-07-14 13:03:05 UTC
Parallelism
84/100
Blocked
50%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,705,080 · 32 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
1w05w17w19w211w012w113w215w017w120w021w122w224w327w128w130w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0xb00a78a3…93f9
0xd32edf…ff58
5 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0x2d82ac…5fd8
4 touches
1 conflict
0x00000000…0001
0x2d82ac…5fd8
4 touches
1 conflict
0x38b5b2ce…c5bb
0x2d82ac…5fd8
4 touches
1 conflict
0x0a76de9e…e4b6
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity