← previous blocknext block →recent activity

Analyzing

Block #74,655,297

37 transactions · 22 stateful · 2026-05-15 01:46:02 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

0.95

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,655,297  ·  37 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x3145aad0…29a4

0xd32edf…ff58

13 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x6f2e60dc…e661

0x34b655…2a6f

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

21 conflicts on slot 0x3145aad0cb…7629a4

← previous block·next block →recent activity