← previous blocknext block →recent activity

Analyzing

Block #87,738,533

22 transactions · 18 stateful · 2026-07-14 16:47:03 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.14

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,738,533  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x46e3da6b…72ca

0x34b655…2a6f

12 touches
15 conflicts

0x60dc7b78…d1d5

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x94ba9c4a…41d8

0x34b655…2a6f

6 touches
3 conflicts

0x9c3004b2…5421

0x34b655…2a6f

6 touches
3 conflicts

0x5c79a7db…b7aa

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xebe9512d…5162

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 0x46e3da6bf9…ac72ca

← previous block·next block →recent activity