← previous blocknext block →recent activity

Analyzing

Block #92,973,256

18 transactions · 16 stateful · 2026-08-04 05:07:29 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,973,256  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xa56e54d0…2d39

0x34b655…2a6f

6 touches
3 conflicts

0xce06a0f7…efef

0x34b655…2a6f

6 touches
3 conflicts

0x7344e931…6a3c

0xd32edf…ff58

5 touches
3 conflicts

0x40d2f403…d0bc

0x34b655…2a6f

5 touches
3 conflicts

0x34a1ee7e…fb20

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

10 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity