← previous blocknext block →recent activity

Analyzing

Block #73,034,904

38 transactions · 27 stateful · 2026-05-07 13:36:50 UTC

Parallelism

66/100

Blocked

63%

Avg conflicts / tx

1.61

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,034,904  ·  38 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x388e001a…7e04

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x23951077…539b

0x34b655…2a6f

8 touches
6 conflicts

0x5dc14a96…6816

0x34b655…2a6f

8 touches
6 conflicts

0xaef9058e…322a

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

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity