← previous blocknext block →recent activity

Analyzing

Block #74,400,376

12 transactions · 10 stateful · 2026-05-13 21:21:10 UTC

Parallelism

83/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,400,376  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd40bddc1…773c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa02838a3…bc54

0x34b655…2a6f

4 touches
1 conflict

0x21d5695a…a023

0x1c921c…0f5b

2 touches
0 conflicts

0x2569078d…1c40

0x1c921c…0f5b

2 touches
0 conflicts

0x3f7d44ef…c7a8

0x1c921c…0f5b

2 touches
0 conflicts

0xb522ef34…bada

0x1c921c…0f5b

2 touches
0 conflicts

0xf792458c…37b4

0x1c921c…0f5b

2 touches
0 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

1 conflict on slot 0xd40bddc144…4e773c

← previous block·next block →recent activity