← previous blocknext block →recent activity

Analyzing

Block #74,722,082

40 transactions · 24 stateful · 2026-05-15 09:11:24 UTC

Parallelism

88/100

Blocked

50%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,722,082  ·  40 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x77a2b233…c920

0xd32edf…ff58

9 touches
10 conflicts

0xa02838a3…bc54

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xc613436a…63cd

0x34b655…2a6f

6 touches
3 conflicts

0xbea1a832…7b9c

0x34b655…2a6f

6 touches
3 conflicts

0x26a58d61…a078

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0003

0x63e48b…53f2

4 touches
1 conflict

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

10 conflicts on slot 0x77a2b233b8…e3c920

← previous block·next block →recent activity