← previous blocknext block →recent activity

Analyzing

Block #95,201,297

21 transactions · 20 stateful · 2026-08-12 00:12:19 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,201,297  ·  21 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

0x0a57a2b8…3cdd

0x34b655…2a6f

10 touches
10 conflicts

0x0d2de0f6…e6c6

0x34b655…2a6f

6 touches
3 conflicts

0xb519996d…4224

0x34b655…2a6f

6 touches
3 conflicts

0x7bcd679c…954d

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x948836ff…59ab

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

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

10 conflicts on slot 0x0a57a2b8cd…773cdd

← previous block·next block →recent activity