← previous blocknext block →recent activity

Analyzing

Block #75,427,107

19 transactions · 11 stateful · 2026-05-18 15:42:51 UTC

Parallelism

79/100

Blocked

45%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,427,107  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x451e482b…7e7d

0x34b655…2a6f

6 touches
3 conflicts

0x56b77119…eefa

0xd32edf…ff58

5 touches
3 conflicts

0x65e795ca…0320

0x34b655…2a6f

4 touches
1 conflict

0xa8acb3bb…6984

0x34b655…2a6f

4 touches
1 conflict

0x0cad650f…0ff3

0x34b655…2a6f

4 touches
1 conflict

0x8d0e98f3…7ba0

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity