← previous blocknext block →recent activity

Analyzing

Block #91,999,856

20 transactions · 19 stateful · 2026-07-31 19:30:12 UTC

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,999,856  ·  20 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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x3732c6c9…ded6

0x34b655…2a6f

4 touches
1 conflict

0x39894b51…3263

0x34b655…2a6f

4 touches
1 conflict

0x42b10c57…3ee7

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x632a3f89…c958

0x34b655…2a6f

4 touches
1 conflict

0x6a192d91…d497

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

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

3 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity