← previous blocknext block →recent activity

Analyzing

Block #87,620,700

34 transactions · 31 stateful · 2026-07-14 03:38:53 UTC

Parallelism

56/100

Blocked

68%

Avg conflicts / tx

1.97

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #87,620,700  ·  34 txs across 15 waves  ·  depth 15
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

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

0x925c118c…a1d8

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xc514314c…1aa4

0x34b655…2a6f

10 touches
10 conflicts

0x05dabb1a…f91e

0x34b655…2a6f

10 touches
10 conflicts

0x745952b2…d90c

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

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

10 conflicts on slot 0x925c118c7b…bea1d8

← previous block·next block →recent activity