← previous blocknext block →recent activity

Analyzing

Block #95,523,242

19 transactions · 16 stateful · 2026-08-13 03:25:14 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,523,242  ·  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

0x98cfeec2…d6e5

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x9dd0a735…4d04

0x34b655…2a6f

6 touches
3 conflicts

0x524f0872…0d12

0x34b655…2a6f

4 touches
1 conflict

0xa9a9d0e0…4087

0x34b655…2a6f

4 touches
1 conflict

0xa9af9157…5a6e

0x34b655…2a6f

4 touches
1 conflict

0xab7f4e6b…8093

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 0x98cfeec2c7…d1d6e5

← previous block·next block →recent activity