← previous blocknext block →recent activity

Analyzing

Block #92,646,894

19 transactions · 17 stateful · 2026-08-03 01:44:22 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

1.21

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #92,646,894  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0x427d1120…4eb1

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xe9457301…83cd

0x34b655…2a6f

6 touches
3 conflicts

0x85971f5d…e920

0x34b655…2a6f

6 touches
3 conflicts

0x513677c7…80eb

0x34b655…2a6f

6 touches
3 conflicts

0x6f8644f7…10fa

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity