← previous blocknext block →recent activity
Analyzing
Block #87,497,452
25 transactions · 20 stateful · 2026-07-13 13:53:50 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,497,452 · 25 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
1w03w07w08w110w011w112w216w017w118w119w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d835685…6f24
0x34b655…2a6f
6 touches
3 conflicts
0x571cb36d…3b3d
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x85ac0ab8…a3d8
0x34b655…2a6f
6 touches
3 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x696538f2…99c9
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 0x4d8356853b…a26f24
Audit this contract →
← previous block·next block →recent activity