← previous blocknext block →recent activity

Analyzing

Block #94,791,522

21 transactions · 20 stateful · 2026-08-10 13:50:21 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,791,522  ·  21 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

0xd2ffa1f3…d3ae

0x34b655…2a6f

6 touches
3 conflicts

0x4bfdcd51…9b58

0x34b655…2a6f

4 touches
1 conflict

0x6c26d635…1bbf

0x34b655…2a6f

4 touches
1 conflict

0x808129fc…f97d

0x34b655…2a6f

4 touches
1 conflict

0x8faba3a7…8454

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xeae24c…0be0

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