← previous blocknext block →recent activity

Analyzing

Block #87,357,179

22 transactions · 21 stateful · 2026-07-12 22:15:43 UTC

Parallelism

68/100

Blocked

57%

Avg conflicts / tx

1.41

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,357,179  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xfaef08b1…0696

0x34b655…2a6f

14 touches
21 conflicts

0x8a35acfb…d1ac

0xb1dbf0…c0d3

8 touches
6 conflicts

0x727fbce7…0c80

0x34b655…2a6f

6 touches
3 conflicts

0x74505703…2f07

0x34b655…2a6f

6 touches
3 conflicts

0x7506443a…4820

0x34b655…2a6f

6 touches
3 conflicts

0x8cc1393f…07fb

0x34b655…2a6f

6 touches
3 conflicts

0x93b6fab0…09d6

0x34b655…2a6f

6 touches
3 conflicts

0xb0bc3bf8…e2b1

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

21 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity