← previous blocknext block →recent activity

Analyzing

Block #75,679,570

8 transactions · 7 stateful · 2026-05-19 19:55:08 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,679,570  ·  8 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x309ef367…e8a1

0x34b655…2a6f

4 touches
1 conflict

0xb7b446d2…2006

0x34b655…2a6f

4 touches
1 conflict

0xb4ead3cb…26ef

0x1efe02…37d6

2 touches
0 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

0x1c0eecd7…992b

0x34b655…2a6f

2 touches
0 conflicts

0x1005f9aa…8bfc

0xea1b8e…c5ec

2 touches
0 conflicts

0x1005f9aa…8bff

0xea1b8e…c5ec

2 touches
0 conflicts

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

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity