← previous blocknext block →recent activity

Analyzing

Block #92,561,981

21 transactions · 20 stateful · 2026-08-02 18:37:16 UTC

Parallelism

57/100

Blocked

50%

Avg conflicts / tx

1.33

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #92,561,981  ·  21 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0xf3d10975…0d07

0x34b655…2a6f

10 touches
10 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

10 touches
10 conflicts

0x3aae83ca…8cc1

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x91b0f8ed…6bd7

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity