← previous blocknext block →recent activity

Analyzing

Block #87,303,599

20 transactions · 17 stateful · 2026-07-12 16:17:27 UTC

Parallelism

50/100

Blocked

59%

Avg conflicts / tx

2.4

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #87,303,599  ·  20 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

16 touches
28 conflicts

0x737acb78…fce8

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0x92385428…6941

0x34b655…2a6f

12 touches
15 conflicts

0x0733be30…112f

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xa05444cf…cd70

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4ab

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

28 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity