← previous blocknext block →recent activity

Analyzing

Block #92,525,656

18 transactions · 17 stateful · 2026-08-02 15:34:36 UTC

Parallelism

61/100

Blocked

59%

Avg conflicts / tx

1.17

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #92,525,656  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xd0f945f2…76ed

0xd32edf…ff58

7 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x6c60fbcf…8744

0x34b655…2a6f

6 touches
3 conflicts

0xd6c771f7…6bb1

0x34b655…2a6f

6 touches
3 conflicts

0x7e1faa73…bfbf

0x34b655…2a6f

6 touches
3 conflicts

0xbdc80bf7…e947

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

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 0xc824469a90…af6425

← previous block·next block →recent activity