← previous blocknext block →recent activity
Analyzing
Block #87,707,678
34 transactions · 26 stateful · 2026-07-14 13:20:29 UTC
Parallelism
88/100
Blocked
46%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,707,678 · 34 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
2w03w05w06w19w112w213w016w117w018w119w220w323w125w126w227w331w032w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xfa551be3…a911
0xa6afd3…d132
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x2385516f…eca5
0x34b655…2a6f
4 touches
1 conflict
0x2b5cb9f0…1d10
0x34b655…2a6f
4 touches
1 conflict
0x48315f67…c1a6
0x34b655…2a6f
4 touches
1 conflict
0x6603ed8d…cde2
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity