← previous blocknext block →recent activity

Analyzing

Block #75,205,311

15 transactions · 14 stateful · 2026-05-17 14:58:51 UTC

Parallelism

67/100

Blocked

43%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,205,311  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x3e49348b…9445

0x34b655…2a6f

8 touches
6 conflicts

0x8fbde2b3…9b8f

0x34b655…2a6f

6 touches
3 conflicts

0x1c1e24b9…99d8

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x5b92f676…1b0a

0x34b655…2a6f

4 touches
1 conflict

0x65e795ca…0320

0x34b655…2a6f

4 touches
1 conflict

0xcf55ee9e…efaf

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: 0x34b6552d…112a6f

6 conflicts on slot 0x3e49348b38…839445

← previous block·next block →recent activity