← previous blocknext block →recent activity
Analyzing
Block #87,524,584
31 transactions · 29 stateful · 2026-07-13 16:55:57 UTC
Parallelism
87/100
Blocked
28%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,524,584 · 31 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
4w06w08w19w210w311w112w218w124w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x571cb36d…3b3d
0x34b655…2a6f
8 touches
6 conflicts
0x1b2c54a1…5a76
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x85ac0ab8…a3d8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa535ecc7…c0e0
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0x571cb36db3…a33b3d
Audit this contract →
← previous block·next block →recent activity