← previous blocknext block →recent activity

Analyzing

Block #92,752,719

16 transactions · 16 stateful · 2026-08-03 10:37:46 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,752,719  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x3a9e59a0…6198

0x34b655…2a6f

6 touches
3 conflicts

0x0e0c66fe…796f

0x1e2721…7805

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x1f6f8ff8…a5d4

0x34b655…2a6f

4 touches
1 conflict

0x1f6f8ff8…a5d5

0x34b655…2a6f

4 touches
1 conflict

0x341f69b9…c21b

0x34b655…2a6f

4 touches
1 conflict

0x56de7db5…d21d

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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

3 conflicts on slot 0x3a9e59a03d…4e6198

← previous block·next block →recent activity