← previous blocknext block →recent activity

Analyzing

Block #91,763,026

26 transactions · 20 stateful · 2026-07-30 23:38:47 UTC

Parallelism

85/100

Blocked

25%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,763,026  ·  26 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

0x3439dfbc…0d03

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x2da28f3b…cc6e

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x21d22421…0b7a

0x34b655…2a6f

4 touches
1 conflict

0x2e153698…5b40

0x34b655…2a6f

4 touches
1 conflict

0x7bbc8001…d537

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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 0x3439dfbcc6…080d03

← previous block·next block →recent activity