← previous blocknext block →recent activity

Analyzing

Block #95,124,670

21 transactions · 19 stateful · 2026-08-11 17:46:55 UTC

Parallelism

67/100

Blocked

42%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,124,670  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x745952b2…d90c

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x2385516f…eca5

0x34b655…2a6f

6 touches
3 conflicts

0x217bd767…b79e

0x34b655…2a6f

6 touches
3 conflicts

0x4c188934…158e

0x34b655…2a6f

6 touches
3 conflicts

0x2533f477…a43b

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e66

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

6 conflicts on slot 0x745952b2a0…a6d90c

← previous block·next block →recent activity