← previous blocknext block →recent activity

Analyzing

Block #96,290,731

12 transactions · 10 stateful · 2026-08-15 19:47:05 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,290,731  ·  12 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

0xcb21158b…f18d

0x34b655…2a6f

4 touches
1 conflict

0xdd98c4f0…6ebf

0x34b655…2a6f

4 touches
1 conflict

0xf5c75a87…787c

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x4d4389b2…6e07

0x34b655…2a6f

4 touches
1 conflict

0xa457c06e…2f06

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0xcb21158b83…66f18d

← previous block·next block →recent activity