← previous blocknext block →recent activity

Analyzing

Block #87,496,519

22 transactions · 20 stateful · 2026-07-13 13:47:35 UTC

Parallelism

59/100

Blocked

55%

Avg conflicts / tx

1.32

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,496,519  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x4c188934…158e

0x34b655…2a6f

10 touches
10 conflicts

0x53f393fa…00b9

0x34b655…2a6f

8 touches
6 conflicts

0x2a49f3bf…713b

0x34b655…2a6f

6 touches
3 conflicts

0x326d4924…1788

0x34b655…2a6f

6 touches
3 conflicts

0x32dfa6a9…12f6

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x08330b36…ae29

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 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 0x4c18893450…c5158e

← previous block·next block →recent activity