← previous blocknext block →recent activity

Analyzing

Block #95,371,479

31 transactions · 30 stateful · 2026-08-12 14:40:17 UTC

Parallelism

61/100

Blocked

57%

Avg conflicts / tx

1.9

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #95,371,479  ·  31 txs across 12 waves  ·  depth 12
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

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

0xefa65ccf…1078

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xbde524f4…43bf

0x34b655…2a6f

10 touches
10 conflicts

0x3439dfbc…0d03

0x34b655…2a6f

10 touches
10 conflicts

0x0bd95eb4…e562

0x34b655…2a6f

8 touches
6 conflicts

0x5fab7fbe…1ce5

0x34b655…2a6f

8 touches
6 conflicts

0x74137b07…5880

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 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 0xefa65ccf52…131078

← previous block·next block →recent activity