← previous blocknext block →recent activity

Analyzing

Block #74,918,653

38 transactions · 24 stateful · 2026-05-16 07:03:45 UTC

Parallelism

68/100

Blocked

63%

Avg conflicts / tx

2.03

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,918,653  ·  38 txs across 12 waves  ·  depth 12
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

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

0xa9826933…684a

0xd32edf…ff58

23 touches
66 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

10 touches
10 conflicts

0x00f7e3b7…e017

0x188d58…ea8e

10 touches
10 conflicts

0x56a919c4…ab49

0xee8c0e…1242

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb85

0x1b6862…e19c

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

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

66 conflicts on slot 0xa9826933f4…b7684a

← previous block·next block →recent activity