← previous blocknext block →recent activity

Analyzing

Block #87,525,016

19 transactions · 18 stateful · 2026-07-13 16:58:51 UTC

Parallelism

53/100

Blocked

61%

Avg conflicts / tx

1.84

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,525,016  ·  19 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

0x24f6d4ca…c33b

0x34b655…2a6f

12 touches
15 conflicts

0x2a49f3bf…713b

0x34b655…2a6f

8 touches
6 conflicts

0x3a6290da…e683

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x2b4f426d…5de5

0x34b655…2a6f

6 touches
3 conflicts

0x53f393fa…00b9

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

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

15 conflicts on slot 0x24f6d4ca30…1ec33b

← previous block·next block →recent activity