← previous blocknext block →recent activity

Analyzing

Block #73,647,574

16 transactions · 13 stateful · 2026-05-10 09:34:50 UTC

Parallelism

63/100

Blocked

46%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,647,574  ·  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

0x0032faf9…de04

0x34b655…2a6f

12 touches
15 conflicts

0xd49762c9…1359

0x34b655…2a6f

10 touches
10 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

10 touches
10 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

10 touches
10 conflicts

0xedb848fe…6534

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

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

15 conflicts on slot 0x0032faf96a…e8de04

← previous block·next block →recent activity