← previous blocknext block →recent activity

Analyzing

Block #91,905,184

17 transactions · 15 stateful · 2026-07-31 11:34:01 UTC

Parallelism

76/100

Blocked

20%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,905,184  ·  17 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

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xab088a08…2ef0

0x34b655…2a6f

6 touches
3 conflicts

0x78541caf…bfec

0x34b655…2a6f

4 touches
1 conflict

0x809f2ba8…89d3

0x34b655…2a6f

4 touches
1 conflict

0x8d175439…fb79

0x34b655…2a6f

4 touches
1 conflict

0x9cf9008a…d826

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 0xd66696e0dc…230842

← previous block·next block →recent activity