← previous blocknext block →recent activity

Analyzing

Block #73,846,361

9 transactions · 9 stateful · 2026-05-11 07:52:07 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,846,361  ·  9 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x89999c15…fdac

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x1c0c885d…7272

0x065c9d…c394

2 touches
0 conflicts

0x2a823462…e0d2

0x065c9d…c394

2 touches
0 conflicts

0x2b2ed51e…ff66

0x065c9d…c394

2 touches
0 conflicts

0x5918eb51…ba6c

0x065c9d…c394

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity