← previous blocknext block →recent activity

Analyzing

Block #95,572,525

24 transactions · 23 stateful · 2026-08-13 07:33:07 UTC

Parallelism

88/100

Blocked

26%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,572,525  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xa39ce2ef…93dc

0x968279…9342

6 touches
3 conflicts

0x521a5982…a82a

0x754704…b603

6 touches
3 conflicts

0x00000000…0006

0x968279…9342

6 touches
3 conflicts

0x229ed15d…cae4

0x968279…9342

6 touches
3 conflicts

0x229ed15d…cae5

0x968279…9342

6 touches
3 conflicts

0x229ed15d…cae8

0x968279…9342

6 touches
3 conflicts

0x229ed15d…cae9

0x968279…9342

6 touches
3 conflicts

0x229ed15d…caea

0x968279…9342

6 touches
3 conflicts

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: 0x96827978…f09342

3 conflicts on slot 0xa39ce2ef64…fc93dc

← previous block·next block →recent activity