← previous blocknext block →recent activity

Analyzing

Block #87,704,200

21 transactions · 19 stateful · 2026-07-14 12:57:12 UTC

Parallelism

57/100

Blocked

53%

Avg conflicts / tx

1.67

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,704,200  ·  21 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x6fe7d366…78ff

0x34b655…2a6f

14 touches
21 conflicts

0x8fe37a3f…4c89

0x34b655…2a6f

14 touches
21 conflicts

0x4f51d069…d0b4

0x34b655…2a6f

12 touches
15 conflicts

0xeeaba9d3…b491

0x34b655…2a6f

12 touches
15 conflicts

0xbf68b5d2…0eba

0x34b655…2a6f

12 touches
15 conflicts

0x67905f6e…02a1

0x34b655…2a6f

12 touches
15 conflicts

0x5b145de0…367c

0xc8689a…ee79

12 touches
15 conflicts

0x0e3e9dbd…7c82

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity