← previous blocknext block →recent activity

Analyzing

Block #74,775,671

32 transactions · 25 stateful · 2026-05-15 15:10:01 UTC

Parallelism

78/100

Blocked

60%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,775,671  ·  32 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0001

0xcc67aa…c71c

6 touches
3 conflicts

0x58b97bee…70dd

0x065c9d…c394

6 touches
3 conflicts

0x75f6889e…7f1e

0x34b655…2a6f

6 touches
3 conflicts

0x00c46468…f328

0x3bd359…433a

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0x44ad89ba…cf83

0x5c2513…7777

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: 0x34b6552d…112a6f

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity