← previous blocknext block →recent activity
Analyzing
Block #87,506,439
23 transactions · 19 stateful · 2026-07-13 14:54:00 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,506,439 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w18w09w110w211w215w316w420w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eeb2a30…6909
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x079a347d…d721
0x34b655…2a6f
4 touches
1 conflict
0x103f3294…1abb
0x34b655…2a6f
4 touches
1 conflict
0x156b161b…ef04
0x34b655…2a6f
4 touches
1 conflict
0x3ff28ef7…e395
0x34b655…2a6f
4 touches
1 conflict
0x4293a398…286e
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 0x0eeb2a3089…8a6909
Audit this contract →
← previous block·next block →recent activity