← previous blocknext block →recent activity

Analyzing

Block #95,655,021

19 transactions · 18 stateful · 2026-08-13 14:28:04 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,655,021  ·  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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x1a5d321d…a474

0x34b655…2a6f

6 touches
3 conflicts

0xf0d45ffd…89cf

0x34b655…2a6f

6 touches
3 conflicts

0x9fd372a1…a959

0x34b655…2a6f

6 touches
3 conflicts

0x1565183a…e0a0

0x34b655…2a6f

4 touches
1 conflict

0x45413140…8184

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

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 0xca841faae5…71486a

← previous block·next block →recent activity