← previous blocknext block →recent activity

Analyzing

Block #74,609,343

31 transactions · 26 stateful · 2026-05-14 20:39:40 UTC

Parallelism

71/100

Blocked

62%

Avg conflicts / tx

1.16

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,609,343  ·  31 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

0xadac4a86…c2bc

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x3da91649…f9be

0xd32edf…ff58

9 touches
10 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0xce8bbe33…b72e

0x3bd359…433a

6 touches
3 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0x309ef367…e8a1

0x34b655…2a6f

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

10 conflicts on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity