← previous blocknext block →recent activity

Analyzing

Block #75,091,868

21 transactions · 20 stateful · 2026-05-17 02:21:37 UTC

Parallelism

52/100

Blocked

70%

Avg conflicts / tx

1.67

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #75,091,868  ·  21 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xb9868b52…c77f

0x34b655…2a6f

8 touches
6 conflicts

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0x2c1a56ba…2061

0x34b655…2a6f

6 touches
3 conflicts

0xc4eb89d3…ddad

0x34b655…2a6f

6 touches
3 conflicts

0x1772f8c0…6be8

0x065c9d…c394

5 touches
3 conflicts

0x664bf99e…0a8c

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity