← previous blocknext block →recent activity

Analyzing

Block #95,386,978

23 transactions · 21 stateful · 2026-08-12 15:58:46 UTC

Parallelism

52/100

Blocked

62%

Avg conflicts / tx

1.57

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #95,386,978  ·  23 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x4cabb80a…46bf

0x34b655…2a6f

12 touches
15 conflicts

0x66d5e476…8a1f

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xce06a0f7…efef

0x34b655…2a6f

6 touches
3 conflicts

0x1c6b043d…d294

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

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

15 conflicts on slot 0x4cabb80a0e…7546bf

← previous block·next block →recent activity