← previous blocknext block →recent activity

Analyzing

Block #74,762,457

23 transactions · 20 stateful · 2026-05-15 13:41:31 UTC

Parallelism

83/100

Blocked

45%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,762,457  ·  23 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

0x8a2f9a36…fb4a

0xfa32f9…f3f0

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x99f666e3…b2a2

0x3bd359…433a

6 touches
3 conflicts

0x9194f4a3…10b8

0x754704…b603

6 touches
3 conflicts

0x00000000…0000

0xfa32f9…f3f0

6 touches
3 conflicts

0x00000000…0001

0xfa32f9…f3f0

6 touches
3 conflicts

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0xe4b233e4…db14

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: 0xfa32f9ec…fef3f0

3 conflicts on slot 0x8a2f9a362c…60fb4a

← previous block·next block →recent activity