← previous blocknext block →recent activity

Analyzing

Block #73,657,797

31 transactions · 19 stateful · 2026-05-10 10:43:45 UTC

Parallelism

90/100

Blocked

32%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,657,797  ·  31 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

0xae69c125…2379

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x38524fae…9deb

0x34b655…2a6f

6 touches
3 conflicts

0x69b9470f…1b5b

0x065c9d…c394

6 touches
3 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x5138188e…796b

0x34b655…2a6f

4 touches
1 conflict

0x2ad0f4b3…6b5b

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xae69c12575…722379

← previous block·next block →recent activity