← previous blocknext block →recent activity

Analyzing

Block #87,905,577

20 transactions · 19 stateful · 2026-07-15 11:24:23 UTC

Parallelism

55/100

Blocked

47%

Avg conflicts / tx

1.3

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,905,577  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x84585d11…6ae7

0x34b655…2a6f

8 touches
6 conflicts

0xa0a5bed4…1d15

0x34b655…2a6f

6 touches
3 conflicts

0xf28cf8dc…b0ca

0x34b655…2a6f

6 touches
3 conflicts

0x16757a18…3f40

0x34b655…2a6f

4 touches
1 conflict

0x2b4f0d76…36dd

0x34b655…2a6f

4 touches
1 conflict

0x40080907…45cc

0x34b655…2a6f

4 touches
1 conflict

0x435b08b5…d84e

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity