← previous blocknext block →recent activity

Analyzing

Block #95,114,173

21 transactions · 17 stateful · 2026-08-11 16:54:07 UTC

Parallelism

57/100

Blocked

53%

Avg conflicts / tx

1.33

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #95,114,173  ·  21 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0x5fe7e126…6dd2

0x34b655…2a6f

6 touches
3 conflicts

0xe4f5cdcb…d942

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xa56e54d0…2d39

0x34b655…2a6f

6 touches
3 conflicts

0x312c6e56…3d7a

0x34b655…2a6f

4 touches
1 conflict

0x3fff7ccd…5a48

0x34b655…2a6f

4 touches
1 conflict

0x41675764…22a6

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity