← previous blocknext block →recent activity

Analyzing

Block #87,904,913

16 transactions · 16 stateful · 2026-07-15 11:19:58 UTC

Parallelism

50/100

Blocked

63%

Avg conflicts / tx

1.25

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,904,913  ·  16 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xa0a5bed4…1d15

0x34b655…2a6f

6 touches
3 conflicts

0x067c61b8…650f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x3464bbc5…a323

0xa6afd3…d132

6 touches
3 conflicts

0xf219f7cf…7379

0xa6afd3…d132

6 touches
3 conflicts

0x5a7eb2ab…75a0

0x34b655…2a6f

4 touches
1 conflict

0x64aaadbf…f9f3

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity