← previous blocknext block →recent activity

Analyzing

Block #74,770,314

27 transactions · 19 stateful · 2026-05-15 14:34:10 UTC

Parallelism

59/100

Blocked

53%

Avg conflicts / tx

1.37

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,770,314  ·  27 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xf5dd2465…25d2

0xd32edf…ff58

15 touches
28 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x765c236f…ff45

0x2a68ba…90c5

8 touches
6 conflicts

0xd09e9595…8814

0x065c9d…c394

8 touches
6 conflicts

0xd996735f…8730

0x1b6862…e19c

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0xc9285c38…f6d8

0x699abc…6a3b

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

28 conflicts on slot 0xf5dd246521…4225d2

← previous block·next block →recent activity