← previous blocknext block →recent activity
Analyzing
Block #86,708,738
30 transactions · 26 stateful · 2026-07-09 22:01:03 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,708,738 · 30 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
2w03w15w26w310w011w114w216w317w318w119w420w525w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70ff9262…8d80
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9da6e429…074d
0xa6afd3…d132
8 touches
6 conflicts
0xfc578b53…9b1f
0xa6afd3…d132
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x5b9559b3…cef6
0xa6afd3…d132
5 touches
3 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 0x70ff92623d…f38d80
Audit this contract →
← previous block·next block →recent activity