← previous blocknext block →recent activity

Analyzing

Block #88,185,641

24 transactions · 23 stateful · 2026-07-16 18:38:24 UTC

Parallelism

58/100

Blocked

48%

Avg conflicts / tx

1.25

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #88,185,641  ·  24 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

10 touches
10 conflicts

0xd6419ef2…1643

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xa55c4598…2988

0x34b655…2a6f

8 touches
6 conflicts

0x53f393fa…00b9

0x34b655…2a6f

8 touches
6 conflicts

0x64a785e4…0110

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

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

10 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity