← previous blocknext block →recent activity

Analyzing

Block #73,705,603

17 transactions · 16 stateful · 2026-05-10 16:06:15 UTC

Parallelism

59/100

Blocked

50%

Avg conflicts / tx

1.35

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,705,603  ·  17 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

0x529acb6a…fcc6

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0x7e31cbfd…2505

0x065c9d…c394

6 touches
3 conflicts

0x83cdb3fe…59c9

0xd32edf…ff58

5 touches
3 conflicts

0xb2cb2291…fd25

0x065c9d…c394

4 touches
1 conflict

0xe4c30421…048a

0x065c9d…c394

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: 0x065c9d28…a9c394

6 conflicts on slot 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity