← previous blocknext block →recent activity

Analyzing

Block #73,975,053

10 transactions · 7 stateful · 2026-05-11 22:09:29 UTC

Parallelism

60/100

Blocked

43%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,975,053  ·  10 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xb6ed511f…6b68

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xd30a4208…3cd2

0x34b655…2a6f

4 touches
1 conflict

0xb7af7ea3…7d7d

0x34b655…2a6f

4 touches
1 conflict

0x810a3aa2…0227

0x34b655…2a6f

4 touches
1 conflict

0x60a42a5e…9da2

0x34b655…2a6f

2 touches
0 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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity