← previous blocknext block →recent activity

Analyzing

Block #92,525,209

20 transactions · 19 stateful · 2026-08-02 15:32:21 UTC

Parallelism

50/100

Blocked

53%

Avg conflicts / tx

1.85

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #92,525,209  ·  20 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xbde524f4…43bf

0x34b655…2a6f

16 touches
28 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xce06a0f7…efef

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xbaeb3c8d…23b0

0x34b655…2a6f

6 touches
3 conflicts

0xeb91e69a…8102

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

28 conflicts on slot 0xbde524f475…b143bf

← previous block·next block →recent activity