← previous blocknext block →recent activity

Analyzing

Block #73,642,975

15 transactions · 14 stateful · 2026-05-10 09:03:51 UTC

Parallelism

67/100

Blocked

57%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,642,975  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x8a2657f5…e008

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x0520da1d…c88e

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x2b44df50…1681

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 0x046a928e85…e50012

← previous block·next block →recent activity