← previous blocknext block →recent activity

Analyzing

Block #74,190,790

24 transactions · 18 stateful · 2026-05-12 22:07:04 UTC

Parallelism

75/100

Blocked

67%

Avg conflicts / tx

1.08

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,190,790  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xba213adc…4864

0xd32edf…ff58

11 touches
15 conflicts

0x41335ddf…94b9

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xc2aacf41…5503

0x1b6862…e19c

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

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

15 conflicts on slot 0xba213adc0f…084864

← previous block·next block →recent activity