← previous blocknext block →recent activity

Analyzing

Block #92,543,696

13 transactions · 12 stateful · 2026-08-02 17:05:19 UTC

Parallelism

69/100

Blocked

33%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,543,696  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0d397f7c…0b2f

0x34b655…2a6f

4 touches
1 conflict

0x697189d1…ddfe

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x745a7fd6…5fea

0x34b655…2a6f

4 touches
1 conflict

0x7aa5d2c4…d6ef

0x34b655…2a6f

4 touches
1 conflict

0x859fe39d…effa

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