← previous blocknext block →recent activity

Analyzing

Block #74,774,291

27 transactions · 15 stateful · 2026-05-15 15:00:46 UTC

Parallelism

67/100

Blocked

60%

Avg conflicts / tx

0.59

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,774,291  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd170349f…dbe8

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

5 touches
3 conflicts

0xb2ed0e91…969a

0x065c9d…c394

5 touches
3 conflicts

0x65bd5770…5ecc

0x1b6862…e19c

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

0xd025d7d7…f05a

0x3bd359…433a

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

6 conflicts on slot 0xd170349f3f…97dbe8

← previous block·next block →recent activity