← previous blocknext block →recent activity
Analyzing
Block #87,718,970
16 transactions · 13 stateful · 2026-07-14 14:36:12 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,718,970 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w110w011w112w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9aa29e0c…eb5b
0x34b655…2a6f
6 touches
3 conflicts
0xa79dadf0…437a
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x08a63efb…b394
0x34b655…2a6f
4 touches
1 conflict
0x2bfb71b5…3a04
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x520f8a31…65c5
0x34b655…2a6f
4 touches
1 conflict
0x520f8a31…65c6
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 0x9aa29e0cee…caeb5b
Audit this contract →
← previous block·next block →recent activity