← previous blocknext block →recent activity

Analyzing

Block #73,978,526

14 transactions · 13 stateful · 2026-05-11 22:32:49 UTC

Parallelism

71/100

Blocked

23%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,978,526  ·  14 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

0x742436a7…c4d4

0x34b655…2a6f

4 touches
1 conflict

0x7c51d9aa…af39

0x34b655…2a6f

4 touches
1 conflict

0x24ed74ea…a3ff

0x34b655…2a6f

4 touches
1 conflict

0x310a7246…2dcb

0x34b655…2a6f

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe22ab637…7a8e

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

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

1 conflict on slot 0x742436a7e5…69c4d4

← previous block·next block →recent activity