← previous blocknext block →recent activity
Analyzing
Block #87,519,385
18 transactions · 17 stateful · 2026-07-13 16:20:48 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,519,385 · 18 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
1w02w13w14w25w06w111w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0be747d5…22e0
0x34b655…2a6f
4 touches
1 conflict
0x0be747d5…22e1
0x34b655…2a6f
4 touches
1 conflict
0x18e900fa…07f4
0x34b655…2a6f
4 touches
1 conflict
0x21d22421…0b7a
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x39bd1fab…a39c
0x34b655…2a6f
4 touches
1 conflict
0x5a6864fe…2890
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
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
1 conflict on slot 0x0be747d5f3…e922e0
Audit this contract →
← previous block·next block →recent activity