← previous blocknext block →recent activity

Analyzing

Block #96,300,939

19 transactions · 14 stateful · 2026-08-15 20:38:25 UTC

Parallelism

89/100

Blocked

21%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #96,300,939  ·  19 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

0x424934c8…f2f1

0x34b655…2a6f

4 touches
1 conflict

0x7660bb2e…eb97

0x34b655…2a6f

4 touches
1 conflict

0x81561f70…fefd

0x34b655…2a6f

4 touches
1 conflict

0xf63c2a2b…bc5f

0x34b655…2a6f

4 touches
1 conflict

0xf63c2a2b…bc60

0x34b655…2a6f

4 touches
1 conflict

0x513b0c80…d2d9

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x98c2a26b…bb8d

0x065c9d…c394

3 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 0x424934c865…4af2f1

← previous block·next block →recent activity