Block #73,681,234

← previous blocknext block →recent activity

Analyzing

Block #73,681,234

30 transactions · 26 stateful · 2026-05-10 13:22:00 UTC

Parallelism

63/100

Blocked

62%

Avg conflicts / tx

2.2

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,681,234  ·  30 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xee94c78f…ee10

0xd32edf…ff58

21 touches
55 conflicts

0xb8228d38…3953

0x34b655…2a6f

8 touches
6 conflicts

0x3e733ae4…4598

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0x2877f440…c2c8

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

55 conflicts on slot 0xee94c78f17…50ee10

← previous block·next block →recent activity