← previous blocknext block →recent activity
Analyzing
Block #87,714,600
26 transactions · 23 stateful · 2026-07-14 14:06:51 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,714,600 · 26 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
2w03w010w011w112w214w018w319w420w121w123w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x572f121e…964f
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xf0571291…b6ca
0x34b655…2a6f
6 touches
3 conflicts
0x0defadc5…70e9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x98aedeb3…243a
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 0x572f121e13…6d964f
Audit this contract →
← previous block·next block →recent activity