← previous blocknext block →recent activity
Analyzing
Block #87,056,280
16 transactions · 14 stateful · 2026-07-11 12:43:42 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,056,280 · 16 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
5w06w17w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xae901867…8086
0x34b655…2a6f
4 touches
1 conflict
0xf60d3c80…c8a7
0x34b655…2a6f
4 touches
1 conflict
0x001b7d74…69e0
0x34b655…2a6f
4 touches
1 conflict
0x253bf197…1e1a
0x34b655…2a6f
4 touches
1 conflict
0x40883ce5…2ae2
0x34b655…2a6f
4 touches
1 conflict
0x49a97bff…33ed
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity