← previous blocknext block →recent activity

Analyzing

Block #92,758,871

20 transactions · 20 stateful · 2026-08-03 11:08:43 UTC

Parallelism

65/100

Blocked

40%

Avg conflicts / tx

1.2

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

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

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x948836ff…59ab

0x34b655…2a6f

6 touches
4 conflicts

0x7d7c8caa…dc36

0x34b655…2a6f

6 touches
4 conflicts

0xe5a38e46…a68c

0x34b655…2a6f

6 touches
3 conflicts

0xf06ab8d8…3589

0x34b655…2a6f

6 touches
3 conflicts

0x05e1eba1…6491

0x34b655…2a6f

4 touches
1 conflict

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 0x482471adbb…39122f

← previous block·next block →recent activity