← previous blocknext block →recent activity

Analyzing

Block #96,038,133

15 transactions · 13 stateful · 2026-08-14 22:36:34 UTC

Parallelism

87/100

Blocked

23%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #96,038,133  ·  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

0xc8b48ea0…b73d

0x968279…9342

4 touches
1 conflict

0xc8b48ea0…b73e

0x968279…9342

4 touches
1 conflict

0xc8b48ea0…b740

0x968279…9342

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x21f14c77…d1fd

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x7ee6007b…fd68

0x34b655…2a6f

4 touches
1 conflict

0x177211e2…1c2d

0x754704…b603

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 0xc8b48ea0c4…6db73d

← previous block·next block →recent activity