← previous blocknext block →recent activity

Analyzing

Block #74,415,728

24 transactions · 16 stateful · 2026-05-13 23:03:20 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,415,728  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x749dc82c…33da

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0003

0x116e7d…d8f1

6 touches
3 conflicts

0x00000000…0000

0x116e7d…d8f1

6 touches
3 conflicts

0xb7143610…adc4

0x3bd359…433a

6 touches
3 conflicts

0x692a4122…76b8

0x350035…7777

6 touches
3 conflicts

0x00000000…0001

0x116e7d…d8f1

6 touches
3 conflicts

0xab2f6eed…254a

0x188d58…ea8e

4 touches
1 conflict

0xd06cc746…27e4

0x350035…7777

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

15 conflicts on slot 0x749dc82cb3…9d33da

← previous block·next block →recent activity