← previous blocknext block →recent activity

Analyzing

Block #74,351,827

46 transactions · 26 stateful · 2026-05-13 15:57:58 UTC

Parallelism

80/100

Blocked

58%

Avg conflicts / tx

0.96

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,351,827  ·  46 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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x21d6593f…26e1

0x34b655…2a6f

8 touches
6 conflicts

0xfc6205fa…4d80

0x34b655…2a6f

8 touches
6 conflicts

0x801a6e57…d85c

0x34b655…2a6f

8 touches
6 conflicts

0x3082c48f…e5fb

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

6 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: 0x34b6552d…112a6f

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity