← previous blocknext block →recent activity
Analyzing
Block #87,282,083
21 transactions · 18 stateful · 2026-07-12 13:53:35 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,282,083 · 21 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
1w02w15w06w17w210w011w012w213w114w216w017w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3413a430…234a
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x006ee1d9…5485
0xa6afd3…d132
6 touches
3 conflicts
0x56fed0dd…581f
0x34b655…2a6f
4 touches
1 conflict
0x56fed0dd…5820
0x34b655…2a6f
4 touches
1 conflict
0x730a64b9…1b00
0x34b655…2a6f
4 touches
1 conflict
0x7a4f47ac…3289
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 0x3413a43072…a1234a
Audit this contract →
← previous block·next block →recent activity