← previous blocknext block →recent activity

Analyzing

Block #75,530,064

15 transactions · 14 stateful · 2026-05-19 03:17:24 UTC

Parallelism

73/100

Blocked

21%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,530,064  ·  15 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

0x309ef367…e8a1

0x34b655…2a6f

4 touches
1 conflict

0x53b4ef2b…8a05

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x3253deba…24f3

0x065c9d…c394

2 touches
0 conflicts

0x576c71c8…95ae

0x065c9d…c394

2 touches
0 conflicts

0x5f77d607…2c84

0x065c9d…c394

2 touches
0 conflicts

0x87ff0328…fea6

0x065c9d…c394

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity