← previous blocknext block →recent activity

Analyzing

Block #73,979,002

19 transactions · 16 stateful · 2026-05-11 22:36:01 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

1.26

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,979,002  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x6f08361d…bda6

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

2 touches
0 conflicts

0x4fe4d51f…835a

0x34b655…2a6f

2 touches
0 conflicts

0x50a88d10…679c

0x34b655…2a6f

2 touches
0 conflicts

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

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity