← previous blocknext block →recent activity

Analyzing

Block #73,043,083

27 transactions · 22 stateful · 2026-05-07 14:31:16 UTC

Parallelism

74/100

Blocked

55%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,043,083  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x1ee8e2d2…4261

0xd32edf…ff58

9 touches
10 conflicts

0xc13c1093…9a9d

0x754704…b603

8 touches
6 conflicts

0xc1ceff4b…04a0

0x3bd359…433a

8 touches
6 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00f7e3b7…e016

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

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

10 conflicts on slot 0x1ee8e2d278…cb4261

← previous block·next block →recent activity