← previous blocknext block →recent activity

Analyzing

Block #96,015,896

15 transactions · 14 stateful · 2026-08-14 20:44:39 UTC

Parallelism

87/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #96,015,896  ·  15 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd51180b1…b87a

0x968279…9342

4 touches
1 conflict

0xd51180b1…b87c

0x968279…9342

4 touches
1 conflict

0x93ed987d…ea03

0x34b655…2a6f

4 touches
1 conflict

0xb4e0a934…5fc7

0x34b655…2a6f

4 touches
1 conflict

0x177211e2…1c2d

0x754704…b603

4 touches
1 conflict

0x521a5982…a82a

0x754704…b603

4 touches
1 conflict

0x00000000…0006

0x968279…9342

4 touches
1 conflict

0xa13db512…f11e

0x968279…9342

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

1 conflict on slot 0xd51180b10a…5db87a

← previous block·next block →recent activity