← previous blocknext block →recent activity

Analyzing

Block #95,173,058

25 transactions · 24 stateful · 2026-08-11 21:50:18 UTC

Parallelism

64/100

Blocked

63%

Avg conflicts / tx

1.88

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #95,173,058  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x424934c8…f2f1

0x34b655…2a6f

14 touches
21 conflicts

0xac2a0273…721b

0x34b655…2a6f

14 touches
21 conflicts

0x737acb78…fce8

0x34b655…2a6f

12 touches
15 conflicts

0x9fd4ce93…ae4e

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xce06a0f7…efef

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 0x424934c865…4af2f1

← previous block·next block →recent activity