← previous blocknext block →recent activity

Analyzing

Block #92,575,340

19 transactions · 16 stateful · 2026-08-02 19:44:27 UTC

Parallelism

63/100

Blocked

56%

Avg conflicts / tx

0.79

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,575,340  ·  19 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

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x3ab93e12…48fc

0x34b655…2a6f

6 touches
3 conflicts

0x0d2de0f6…e6c6

0x34b655…2a6f

6 touches
3 conflicts

0xce06a0f7…efef

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x96dd83e6…a507

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 0x737acb7813…fafce8

← previous block·next block →recent activity