← previous blocknext block →recent activity

Analyzing

Block #94,795,029

23 transactions · 17 stateful · 2026-08-10 14:07:59 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,795,029  ·  23 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

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x3439dfbc…0d03

0x34b655…2a6f

6 touches
3 conflicts

0x5cc231f5…f1cd

0x2b46c0…1669

4 touches
1 conflict

0xb05cd4f5…73d0

0x2b46c0…1669

4 touches
1 conflict

0xe2263bea…6a9d

0x2b46c0…1669

4 touches
1 conflict

0xe2263bea…6aa0

0x2b46c0…1669

4 touches
1 conflict

0xed7dd7db…6022

0x2b46c0…1669

4 touches
1 conflict

0x03aa8b26…118a

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 0xea02471df2…601542

← previous block·next block →recent activity