← previous blocknext block →recent activity

Analyzing

Block #92,431,200

24 transactions · 20 stateful · 2026-08-02 07:39:31 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.46

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #92,431,200  ·  24 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x91b0f8ed…6bd7

0x34b655…2a6f

6 touches
3 conflicts

0x07d94be1…7fa8

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x34b6e036…2161

0x34b655…2a6f

4 touches
1 conflict

0x4abaedb1…65b9

0x34b655…2a6f

4 touches
1 conflict

0x534ef679…ae9d

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

← previous block·next block →recent activity