← previous blocknext block →recent activity

Analyzing

Block #75,478,695

29 transactions · 21 stateful · 2026-05-18 21:26:16 UTC

Parallelism

45/100

Blocked

71%

Avg conflicts / tx

2.45

Longest chain

16 deep

Execution timeline

did this block parallelize well?

view

block #75,478,695  ·  29 txs across 16 waves  ·  depth 16
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

wave w13

wave w14

wave w15

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

0x67650fcf…bd0d

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…0002

0xd2634e…53b1

10 touches
10 conflicts

0x00000000…0003

0xd2634e…53b1

10 touches
10 conflicts

0x00000000…001a

0xd2634e…53b1

10 touches
10 conflicts

0x00000000…001b

0xd2634e…53b1

10 touches
10 conflicts

0x00000000…0022

0xd2634e…53b1

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x969f2d28…4fa2

0x0555e3…2b9c

10 touches
10 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: 0xd32edf66…9fff58

45 conflicts on slot 0x67650fcfd3…88bd0d

← previous block·next block →recent activity