← previous blocknext block →recent activity

Analyzing

Block #92,530,733

19 transactions · 17 stateful · 2026-08-02 16:00:08 UTC

Parallelism

84/100

Blocked

35%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,530,733  ·  19 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

0x34a1ee7e…fb20

0x34b655…2a6f

6 touches
3 conflicts

0x29c1a140…099f

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x7375156d…e2b3

0x34b655…2a6f

5 touches
3 conflicts

0x4bc1abab…5874

0x34b655…2a6f

5 touches
3 conflicts

0x92339d95…0800

0xb1c8ea…8888

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 0x34a1ee7e95…7cfb20

← previous block·next block →recent activity