← previous blocknext block →recent activity

Analyzing

Block #94,809,786

22 transactions · 17 stateful · 2026-08-10 15:22:13 UTC

Parallelism

82/100

Blocked

47%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,809,786  ·  22 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

0x734ee320…caae

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xeae24c…0be0

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0x734ee32053…cecaae

← previous block·next block →recent activity