← previous blocknext block →recent activity

Analyzing

Block #94,811,985

17 transactions · 17 stateful · 2026-08-10 15:33:18 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,811,985  ·  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

0xa6b89ebb…a66e

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x320701d5…f9f3

0x34b655…2a6f

4 touches
1 conflict

0x320701d5…f9f4

0x34b655…2a6f

4 touches
1 conflict

0x5f72d58f…c445

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

1 conflict on slot 0xa6b89ebbaf…5fa66e

← previous block·next block →recent activity