← previous blocknext block →recent activity
Analyzing
Block #87,487,399
20 transactions · 18 stateful · 2026-07-13 12:46:33 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,487,399 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w09w110w211w313w414w215w519w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0x3cb4b659…f735
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x56f6adae…573c
0x34b655…2a6f
6 touches
3 conflicts
0x401a563c…0ae7
0x34b655…2a6f
6 touches
3 conflicts
0x4faeec21…da80
0x34b655…2a6f
4 touches
1 conflict
0x59164e7a…7e0a
0x34b655…2a6f
4 touches
1 conflict
0x76b2f2af…30d6
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
10 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity