← previous blocknext block →recent activity

Analyzing

Block #75,503,300

28 transactions · 25 stateful · 2026-05-19 00:15:09 UTC

Parallelism

53/100

Blocked

72%

Avg conflicts / tx

2.82

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #75,503,300  ·  28 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

20 touches
45 conflicts

0x15698ac9…2a46

0x34b655…2a6f

14 touches
21 conflicts

0xea02471d…1542

0x34b655…2a6f

14 touches
21 conflicts

0xf3a03945…aa1c

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0028

0x1b6862…e19c

8 touches
6 conflicts

0x8b41ec8f…c2d3

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 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

45 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity