← previous blocknext block →recent activity

Analyzing

Block #75,740,771

20 transactions · 18 stateful · 2026-05-20 02:42:14 UTC

Parallelism

60/100

Blocked

72%

Avg conflicts / tx

1.6

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,740,771  ·  20 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

12 touches
15 conflicts

0xe4f0ac52…9a76

0xd32edf…ff58

9 touches
10 conflicts

0x422d5490…52d9

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xe4c6b0cb…0a24

0x1b6862…e19c

6 touches
3 conflicts

0x1c913164…5c2e

0x34b655…2a6f

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity