← previous blocknext block →recent activity

Analyzing

Block #87,752,882

19 transactions · 19 stateful · 2026-07-14 18:23:03 UTC

Parallelism

53/100

Blocked

47%

Avg conflicts / tx

1.42

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,752,882  ·  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

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xf3d10975…0d07

0x34b655…2a6f

10 touches
10 conflicts

0x3f7d8a09…362c

0x34b655…2a6f

8 touches
6 conflicts

0x59dccbd8…2bf6

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x33da0dfa…bac6

0x34b655…2a6f

6 touches
3 conflicts

0x875c3459…2878

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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

10 conflicts on slot 0xea02471df2…601542

← previous block·next block →recent activity