← previous blocknext block →recent activity

Analyzing

Block #92,871,014

26 transactions · 25 stateful · 2026-08-03 20:33:07 UTC

Parallelism

65/100

Blocked

40%

Avg conflicts / tx

1.42

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #92,871,014  ·  26 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

0xb39cb1d8…effa

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0x07d8b1e8…78c6

0x34b655…2a6f

8 touches
6 conflicts

0x7fe8b5d8…3e49

0x34b655…2a6f

6 touches
4 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
4 conflicts

0xcffc17bc…3544

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 0xb39cb1d8c6…28effa

← previous block·next block →recent activity