← previous blocknext block →recent activity

Analyzing

Block #95,153,574

19 transactions · 19 stateful · 2026-08-11 20:12:18 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,153,574  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0672e4a2…8d1f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xbe9baf16…df37

0x34b655…2a6f

6 touches
3 conflicts

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

0x210e0333…9029

0x34b655…2a6f

4 touches
1 conflict

0x371740f5…2ba1

0x34b655…2a6f

4 touches
1 conflict

0x6832000d…5534

0x34b655…2a6f

4 touches
1 conflict

0x83a3f833…8268

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

3 conflicts on slot 0x0672e4a279…2f8d1f

← previous block·next block →recent activity