← previous blocknext block →recent activity

Analyzing

Block #87,753,791

19 transactions · 18 stateful · 2026-07-14 18:29:08 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,753,791  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x644919d7…9727

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2f461725…5ab2

0x34b655…2a6f

6 touches
3 conflicts

0x648bb928…97f2

0x34b655…2a6f

6 touches
3 conflicts

0x39ae60bb…f0be

0x34b655…2a6f

4 touches
1 conflict

0x4327afd2…1b3a

0x34b655…2a6f

4 touches
1 conflict

0x48256a28…fde7

0x34b655…2a6f

4 touches
1 conflict

0x4ade2a65…8adb

0x34b655…2a6f

4 touches
1 conflict

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

6 conflicts on slot 0x644919d7cb…609727

← previous block·next block →recent activity