← previous blocknext block →recent activity

Analyzing

Block #92,574,839

19 transactions · 16 stateful · 2026-08-02 19:41:56 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,574,839  ·  19 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x0e0c66fe…796f

0x1e2721…7805

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x2d3930d3…c9b8

0x34b655…2a6f

4 touches
1 conflict

0x4147b177…c9ba

0x34b655…2a6f

4 touches
1 conflict

0x803eb45d…00bd

0x34b655…2a6f

4 touches
1 conflict

0xdf1473d0…5fea

0x99c7a7…8bf0

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

← previous block·next block →recent activity