← previous blocknext block →recent activity

Analyzing

Block #95,564,584

22 transactions · 20 stateful · 2026-08-13 06:53:10 UTC

Parallelism

77/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,564,584  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x7523c6af…ea66

0x34b655…2a6f

4 touches
1 conflict

0x865a308c…6c35

0x34b655…2a6f

4 touches
1 conflict

0x8f203394…f2db

0x34b655…2a6f

4 touches
1 conflict

0xa1571d54…ae41

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 0x0000000000…0000c9

← previous block·next block →recent activity