← previous blocknext block →recent activity

Analyzing

Block #75,081,622

17 transactions · 12 stateful · 2026-05-17 01:13:07 UTC

Parallelism

53/100

Blocked

58%

Avg conflicts / tx

1.06

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,081,622  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

8 touches
6 conflicts

0x631b4113…baa9

0x34b655…2a6f

6 touches
3 conflicts

0xf072bc14…7472

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x80269196…b9e2

0x34b655…2a6f

4 touches
1 conflict

0x94536a24…dbfd

0x34b655…2a6f

4 touches
1 conflict

0x9c83a7b1…e305

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity