← previous blocknext block →recent activity

Analyzing

Block #87,718,146

22 transactions · 17 stateful · 2026-07-14 14:30:42 UTC

Parallelism

82/100

Blocked

35%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,718,146  ·  22 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x2385516f…eca5

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x53e127a4…c4a6

0x34b655…2a6f

4 touches
1 conflict

0x5985ddc4…eefd

0x34b655…2a6f

4 touches
1 conflict

0x5f234b05…db39

0x34b655…2a6f

4 touches
1 conflict

0x6ac4a9ce…5f63

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

3 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity