← previous blocknext block →recent activity

Analyzing

Block #87,708,215

28 transactions · 26 stateful · 2026-07-14 13:24:05 UTC

Parallelism

53/100

Blocked

62%

Avg conflicts / tx

2.46

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #87,708,215  ·  28 txs across 13 waves  ·  depth 13
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

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

0x8b818135…eff8

0x34b655…2a6f

18 touches
36 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

16 touches
28 conflicts

0x4560e5a8…b741

0x34b655…2a6f

12 touches
15 conflicts

0x5b145de0…367c

0xc8689a…ee79

12 touches
15 conflicts

0x3a68b486…5724

0x34b655…2a6f

12 touches
15 conflicts

0x67905f6e…02a1

0x34b655…2a6f

12 touches
15 conflicts

0x7837c02d…0965

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 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

36 conflicts on slot 0x8b81813549…3ceff8

← previous block·next block →recent activity