← previous blocknext block →recent activity

Analyzing

Block #95,268,839

14 transactions · 12 stateful · 2026-08-12 06:00:49 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,268,839  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00ddbbf2…4588

0x34b655…2a6f

6 touches
3 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

4 touches
1 conflict

0x17c3727d…cb0e

0x34b655…2a6f

4 touches
1 conflict

0x28ceceef…ecc2

0x34b655…2a6f

4 touches
1 conflict

0x3b9bb58c…e73a

0x34b655…2a6f

4 touches
1 conflict

0x5d6e4470…4b4c

0x34b655…2a6f

4 touches
1 conflict

0x6f93faf7…eeca

0x34b655…2a6f

4 touches
1 conflict

0x736bfd85…2594

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

3 conflicts on slot 0x00ddbbf292…ff4588

← previous block·next block →recent activity