← previous blocknext block →recent activity

Analyzing

Block #73,956,378

13 transactions · 9 stateful · 2026-05-11 20:04:56 UTC

Parallelism

77/100

Blocked

44%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,956,378  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xbb12db23…857e

0x34b655…2a6f

4 touches
1 conflict

0xb81d3ee7…3947

0x34b655…2a6f

4 touches
1 conflict

0xcb45d9d6…cb82

0x1b6862…e19c

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0xf111224b…5d55

0xd32edf…ff58

3 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity