← previous blocknext block →recent activity

Analyzing

Block #87,716,404

23 transactions · 22 stateful · 2026-07-14 14:18:59 UTC

Parallelism

70/100

Blocked

41%

Avg conflicts / tx

0.78

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,716,404  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xc0fb0790…a482

0x34b655…2a6f

8 touches
6 conflicts

0x5f43f2bc…e94f

0x34b655…2a6f

6 touches
3 conflicts

0x7525206c…fbd5

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xbf78ee7f…e7fd

0x34b655…2a6f

6 touches
3 conflicts

0x560ed681…07e6

0x34b655…2a6f

4 touches
1 conflict

0x6e859a7c…d0f2

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 0xc0fb0790fb…63a482

← previous block·next block →recent activity