← previous blocknext block →recent activity

Analyzing

Block #75,622,328

18 transactions · 16 stateful · 2026-05-19 13:33:10 UTC

Parallelism

61/100

Blocked

56%

Avg conflicts / tx

1.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,622,328  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xa10c86f8…4b74

0x3bd359…433a

8 touches
6 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

8 touches
6 conflicts

0x00000000…0002

0x019883…2a9a

8 touches
6 conflicts

0x44ad89ba…cf83

0x0cc9b2…7777

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0000

0x019883…2a9a

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity