← previous blocknext block →recent activity

Analyzing

Block #75,340,211

19 transactions · 16 stateful · 2026-05-18 06:01:08 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,340,211  ·  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

0x15698ac9…2a46

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x309ef367…e8a1

0x34b655…2a6f

6 touches
3 conflicts

0xae22cc80…1ce5

0x34b655…2a6f

4 touches
1 conflict

0x28e527c8…c6f2

0x3bd359…433a

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 0x15698ac9db…df2a46

← previous block·next block →recent activity