← previous blocknext block →recent activity

Analyzing

Block #74,505,359

16 transactions · 16 stateful · 2026-05-14 09:00:12 UTC

Parallelism

63/100

Blocked

38%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,505,359  ·  16 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xd11dc26e…59ab

0x34b655…2a6f

8 touches
6 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

6 touches
3 conflicts

0x5aed1bd2…7afa

0x34b655…2a6f

6 touches
3 conflicts

0xa9988419…9f45

0x34b655…2a6f

6 touches
3 conflicts

0xab621973…cc16

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xe181f491…f4e3

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity