← previous blocknext block →recent activity

Analyzing

Block #92,580,054

22 transactions · 17 stateful · 2026-08-02 20:08:11 UTC

Parallelism

82/100

Blocked

41%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,580,054  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x5f6bc8db…0519

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x07bb3f5a…617e

0x34b655…2a6f

4 touches
1 conflict

0x0bd95eb4…e562

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0x442e26a3…e968

0x34b655…2a6f

4 touches
1 conflict

0x4755fafb…859b

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

6 conflicts on slot 0x5f6bc8db1a…f60519

← previous block·next block →recent activity