← previous blocknext block →recent activity

Analyzing

Block #95,206,562

16 transactions · 15 stateful · 2026-08-12 00:38:48 UTC

Parallelism

75/100

Blocked

53%

Avg conflicts / tx

0.81

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,206,562  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x2b54cadb…4425

0xd18b7e…414b

6 touches
3 conflicts

0x0caa5e3f…ea20

0x34b655…2a6f

6 touches
3 conflicts

0xbc66586e…20fe

0x34b655…2a6f

6 touches
3 conflicts

0x33b392cc…4b28

0xd18b7e…414b

4 touches
1 conflict

0x6518075e…2b17

0x2a68ba…90c5

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 0xc824469a90…af6425

← previous block·next block →recent activity