← previous blocknext block →recent activity

Analyzing

Block #73,868,137

23 transactions · 18 stateful · 2026-05-11 10:17:27 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,868,137  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6477c2e0…99ff

0xd32edf…ff58

7 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8a2657f5…e008

0x34b655…2a6f

6 touches
3 conflicts

0x15d039e7…4bb6

0x34b655…2a6f

6 touches
3 conflicts

0x41d3bfa5…523e

0x34b655…2a6f

4 touches
1 conflict

0x4546ebad…b908

0x34b655…2a6f

4 touches
1 conflict

0x64461c10…e86d

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0007

0x1414f3…5137

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: 0xd32edf66…9fff58

6 conflicts on slot 0x6477c2e095…f699ff

← previous block·next block →recent activity