← previous blocknext block →recent activity
Analyzing
Block #87,585,728
22 transactions · 18 stateful · 2026-07-13 23:45:02 UTC
Parallelism
86/100
Blocked
28%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,585,728 · 22 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
2w03w18w09w110w216w017w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f8a50d…333b
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
4 touches
1 conflict
0x7c948aca…6fb9
0x34b655…2a6f
4 touches
1 conflict
0x8252706a…7ca5
0x34b655…2a6f
4 touches
1 conflict
0xad0c7701…1d83
0x34b655…2a6f
4 touches
1 conflict
0xc774ef87…8cfe
0x34b655…2a6f
4 touches
1 conflict
0xe512d5d9…18bc
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x63f8a50db5…53333b
Audit this contract →
← previous block·next block →recent activity