← previous blocknext block →recent activity

Analyzing

Block #95,123,037

18 transactions · 17 stateful · 2026-08-11 17:38:42 UTC

Parallelism

67/100

Blocked

41%

Avg conflicts / tx

1.11

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,123,037  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x745952b2…d90c

0x34b655…2a6f

12 touches
15 conflicts

0xac863d86…4059

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x803eb45d…00bd

0x34b655…2a6f

4 touches
1 conflict

0x944bfd2a…49f7

0x34b655…2a6f

4 touches
1 conflict

0xa0237ed3…2622

0x34b655…2a6f

4 touches
1 conflict

0xa56e54d0…2d39

0x34b655…2a6f

4 touches
1 conflict

0xfde133d7…5e63

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

15 conflicts on slot 0x745952b2a0…a6d90c

← previous block·next block →recent activity