← previous blocknext block →recent activity

Analyzing

Block #92,687,408

20 transactions · 20 stateful · 2026-08-03 05:09:00 UTC

Parallelism

65/100

Blocked

45%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,687,408  ·  20 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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x8a5ced1c…3b29

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

6 touches
3 conflicts

0x02991b41…19e6

0x34b655…2a6f

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0002

0x019883…2a9a

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 0xc824469a90…af6425

← previous block·next block →recent activity