← previous blocknext block →recent activity

Analyzing

Block #74,744,955

36 transactions · 21 stateful · 2026-05-15 11:44:14 UTC

Parallelism

89/100

Blocked

43%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,744,955  ·  36 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x640fcf91…6843

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5ffc25fa…b119

0x34b655…2a6f

6 touches
3 conflicts

0xea57afd0…4232

0x34b655…2a6f

6 touches
3 conflicts

0x2b9c6652…d14e

0x754704…b603

6 touches
3 conflicts

0x3bb4f1c7…ae7c

0xd32edf…ff58

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

6 conflicts on slot 0xdd70bea3b0…701ffe

← previous block·next block →recent activity