← previous blocknext block →recent activity

Analyzing

Block #95,530,247

17 transactions · 16 stateful · 2026-08-13 04:00:28 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,530,247  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8cd684d0…c3cb

0x34b655…2a6f

8 touches
6 conflicts

0x2a9e9bd1…5368

0x2a68ba…90c5

8 touches
6 conflicts

0x2a44a5f4…79b3

0xa6afd3…d132

7 touches
6 conflicts

0x11b69a7e…334e

0xee8c0e…1242

6 touches
3 conflicts

0x24521815…c677

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 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

6 conflicts on slot 0x8cd684d0d7…f5c3cb

← previous block·next block →recent activity