← previous blocknext block →recent activity
Analyzing
Block #87,709,890
16 transactions · 16 stateful · 2026-07-14 13:35:18 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,709,890 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w513w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x015c28a0…37da
0x34b655…2a6f
10 touches
10 conflicts
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0x45e0d4b4…cd58
0x34b655…2a6f
10 touches
10 conflicts
0x5c591136…d322
0x34b655…2a6f
10 touches
10 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
10 touches
10 conflicts
0xacd5183f…6e6d
0x34b655…2a6f
10 touches
10 conflicts
0xbf768a2f…f453
0x34b655…2a6f
10 touches
10 conflicts
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity