← previous blocknext block →recent activity

Analyzing

Block #87,341,974

24 transactions · 22 stateful · 2026-07-12 20:34:05 UTC

Parallelism

63/100

Blocked

55%

Avg conflicts / tx

1.58

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,341,974  ·  24 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

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0x64aaadbf…f9f3

0x34b655…2a6f

12 touches
15 conflicts

0x72880226…1435

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0xfcdb5918…2b49

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0xd1ec0dfd…ccc0

0xc8689a…ee79

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

15 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity