← previous blocknext block →recent activity
Analyzing
Block #87,064,252
15 transactions · 14 stateful · 2026-07-11 13:36:54 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,064,252 · 15 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
1w05w06w19w210w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7012fd2e…ae68
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x593a0f38…b625
0x065c9d…c394
4 touches
1 conflict
0x8a35acfb…d1a9
0xb1dbf0…c0d3
4 touches
1 conflict
0xf3d10975…0d07
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
1 conflict on slot 0x7012fd2edb…cfae68
Audit this contract →
← previous block·next block →recent activity