← previous blocknext block →recent activity

Analyzing

Block #73,920,915

35 transactions · 30 stateful · 2026-05-11 16:09:03 UTC

Parallelism

69/100

Blocked

80%

Avg conflicts / tx

2.23

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,920,915  ·  35 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x58036a86…e2e3

0xd32edf…ff58

17 touches
36 conflicts

0x9ea57326…329f

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

12 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x00000000…0029

0x1b6862…e19c

8 touches
6 conflicts

0x6b1259e6…4e0e

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

36 conflicts on slot 0x58036a863d…cce2e3

← previous block·next block →recent activity