← previous blocknext block →recent activity

Analyzing

Block #92,370,444

18 transactions · 17 stateful · 2026-08-02 02:34:00 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,370,444  ·  18 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

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x5da59c2b…d7b2

0x34b655…2a6f

6 touches
3 conflicts

0xc4d3d66a…d7a8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x3783eb4c…5ad5

0x34b655…2a6f

5 touches
3 conflicts

0x7d0c7575…db47

0x34b655…2a6f

5 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

3 conflicts on slot 0x0000000000…0000c9

← previous block·next block →recent activity