← previous blocknext block →recent activity
Analyzing
Block #87,613,683
16 transactions · 15 stateful · 2026-07-14 02:51:59 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,613,683 · 16 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
1w02w05w06w17w210w111w112w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc807a400…b958
0x34b655…2a6f
6 touches
3 conflicts
0x85c84f98…06d7
0x34b655…2a6f
4 touches
1 conflict
0x91d48be7…e4e8
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9599eb41…b5d6
0x34b655…2a6f
4 touches
1 conflict
0xbabe821d…939b
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity