← previous blocknext block →recent activity
Analyzing
Block #87,587,709
16 transactions · 12 stateful · 2026-07-13 23:58:16 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,587,709 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w18w29w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x346e6e22…8deb
0x34b655…2a6f
4 touches
1 conflict
0x39f71bf7…4269
0x34b655…2a6f
4 touches
1 conflict
0x4780df82…da9f
0x34b655…2a6f
4 touches
1 conflict
0x4780df82…daa0
0x34b655…2a6f
4 touches
1 conflict
0x640530ff…86bc
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity