← previous blocknext block →recent activity

Analyzing

Block #95,203,379

19 transactions · 17 stateful · 2026-08-12 00:22:48 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.58

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,203,379  ·  19 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x2a21d1b9…cb8f

0x34b655…2a6f

4 touches
1 conflict

0x785c87ba…a0f1

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x82dd2252…e1ce

0x34b655…2a6f

4 touches
1 conflict

0x98d1e7bb…8483

0x34b655…2a6f

4 touches
1 conflict

0x33b392cc…4b28

0xd18b7e…414b

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity