← previous blocknext block →recent activity

Analyzing

Block #74,526,905

26 transactions · 21 stateful · 2026-05-14 11:25:21 UTC

Parallelism

81/100

Blocked

52%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,526,905  ·  26 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

0xdd70bea3…1ffe

0x3bd359…433a

8 touches
6 conflicts

0xa764e5f4…e2fd

0xd32edf…ff58

7 touches
6 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0x2b9c6652…d14e

0x754704…b603

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x83ce31c8…22ac

0x34b655…2a6f

4 touches
1 conflict

0x8d0e98f3…7ba0

0x34b655…2a6f

4 touches
1 conflict

0xa8bd52b5…862e

0x34b655…2a6f

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: 0x3bd359c1…15433a

6 conflicts on slot 0xdd70bea3b0…701ffe

← previous block·next block →recent activity