← previous blocknext block →recent activity

Analyzing

Block #95,709,433

22 transactions · 19 stateful · 2026-08-13 19:02:33 UTC

Parallelism

91/100

Blocked

16%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #95,709,433  ·  22 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

0x2328941c…84d3

0x34b655…2a6f

4 touches
1 conflict

0x342e3415…8303

0x34b655…2a6f

4 touches
1 conflict

0x00ddbbf2…4588

0x34b655…2a6f

4 touches
1 conflict

0xcb6ad4a1…b1d8

0x34b655…2a6f

4 touches
1 conflict

0x972e38eb…dc76

0x34b655…2a6f

4 touches
1 conflict

0xee75c266…f8c6

0x34b655…2a6f

4 touches
1 conflict

0x9a9e2858…a685

0x34b655…2a6f

4 touches
1 conflict

0x7dc3c875…76ce

0x34b655…2a6f

2 touches
0 conflicts

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 0x2328941c9c…fc84d3

← previous block·next block →recent activity