← previous blocknext block →recent activity

Analyzing

Block #92,698,736

17 transactions · 15 stateful · 2026-08-03 06:06:01 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,698,736  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x6e30299b…8a4a

0x34b655…2a6f

6 touches
3 conflicts

0x92115abd…ad76

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x43fab434…896f

0xa6afd3…d132

6 touches
3 conflicts

0x8fa9bc45…e08f

0xa6afd3…d132

6 touches
3 conflicts

0x253bf197…1e1a

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity