← previous blocknext block →recent activity

Analyzing

Block #73,693,738

17 transactions · 14 stateful · 2026-05-10 14:46:14 UTC

Parallelism

47/100

Blocked

57%

Avg conflicts / tx

1.82

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,693,738  ·  17 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xfb642775…3077

0xd32edf…ff58

15 touches
28 conflicts

0xae69c125…2379

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x0a6cb118…4ca7

0x1b6862…e19c

6 touches
3 conflicts

0x8fbc5b20…50bd

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

28 conflicts on slot 0xfb64277591…9e3077

← previous block·next block →recent activity