← previous blocknext block →recent activity

Analyzing

Block #95,245,215

42 transactions · 22 stateful · 2026-08-12 03:54:49 UTC

Parallelism

83/100

Blocked

36%

Avg conflicts / tx

0.57

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,245,215  ·  42 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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

12 touches
15 conflicts

0xce54c462…7f74

0x34b655…2a6f

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x37d710c8…45c1

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xd79c9727…1233

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity