← previous blocknext block →recent activity

Analyzing

Block #73,661,290

36 transactions · 20 stateful · 2026-05-10 11:07:12 UTC

Parallelism

61/100

Blocked

70%

Avg conflicts / tx

2.58

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #73,661,290  ·  36 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

0xc0b4b6d5…bb4f

0xd32edf…ff58

27 touches
91 conflicts

0x46cb45de…a567

0x188d58…ea8e

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x2b093939…9087

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

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

91 conflicts on slot 0xc0b4b6d57d…8abb4f

← previous block·next block →recent activity