← previous blocknext block →recent activity

Analyzing

Block #92,790,758

22 transactions · 18 stateful · 2026-08-03 13:49:12 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

0.86

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #92,790,758  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

12 touches
15 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

6 touches
3 conflicts

0x97785d36…2ac5

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x8fdcb946…dc4b

0x34b655…2a6f

4 touches
1 conflict

0xbb84f537…c9b2

0x34b655…2a6f

4 touches
1 conflict

0xc03846bb…73b3

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity