← previous blocknext block →recent activity

Analyzing

Block #95,351,443

38 transactions · 36 stateful · 2026-08-12 12:58:46 UTC

Parallelism

66/100

Blocked

50%

Avg conflicts / tx

1.87

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #95,351,443  ·  38 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x95c47f03…f1bb

0x34b655…2a6f

14 touches
21 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

12 touches
15 conflicts

0x1bf8d2af…d140

0x34b655…2a6f

10 touches
10 conflicts

0xec7d120d…7084

0x34b655…2a6f

10 touches
10 conflicts

0xd676e291…3ecf

0x34b655…2a6f

10 touches
10 conflicts

0x04044393…6c22

0x34b655…2a6f

8 touches
6 conflicts

0x1a5d321d…a474

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

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

21 conflicts on slot 0x95c47f0322…51f1bb

← previous block·next block →recent activity