← previous blocknext block →recent activity

Analyzing

Block #87,732,764

27 transactions · 27 stateful · 2026-07-14 16:08:29 UTC

Parallelism

59/100

Blocked

52%

Avg conflicts / tx

1.78

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #87,732,764  ·  27 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xa55c4598…2988

0x34b655…2a6f

18 touches
36 conflicts

0x3726966a…669d

0x34b655…2a6f

12 touches
15 conflicts

0x5b145de0…367c

0xc8689a…ee79

12 touches
15 conflicts

0x67905f6e…02a1

0x34b655…2a6f

12 touches
15 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0x805d08cf…3cfc

0x34b655…2a6f

12 touches
15 conflicts

0xeeaba9d3…b491

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 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 0xa55c45989b…e52988

← previous block·next block →recent activity