← previous blocknext block →recent activity

Analyzing

Block #75,297,474

25 transactions · 22 stateful · 2026-05-18 01:15:10 UTC

Parallelism

84/100

Blocked

55%

Avg conflicts / tx

0.84

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,297,474  ·  25 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

0xec0f8637…0a93

0xd32edf…ff58

7 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xb63ef486…0dcc

0x34b655…2a6f

4 touches
1 conflict

0xb7b16dd0…0426

0x34b655…2a6f

4 touches
1 conflict

0xb9868b52…c77f

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