← previous blocknext block →recent activity

Analyzing

Block #92,822,293

22 transactions · 21 stateful · 2026-08-03 16:27:50 UTC

Parallelism

55/100

Blocked

48%

Avg conflicts / tx

2

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #92,822,293  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

18 touches
36 conflicts

0xbba9dcbb…e4c9

0x34b655…2a6f

6 touches
3 conflicts

0x94f2c3b4…4ef6

0x34b655…2a6f

6 touches
3 conflicts

0xb25fa8e2…c9ef

0x34b655…2a6f

6 touches
3 conflicts

0xa558e115…fc88

0x34b655…2a6f

6 touches
3 conflicts

0x33b4c2ba…961a

0x34b655…2a6f

6 touches
3 conflicts

0x9de95c94…61c3

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity