← previous blocknext block →recent activity

Analyzing

Block #73,981,408

16 transactions · 13 stateful · 2026-05-11 22:52:13 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,981,408  ·  16 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

0xf6476f21…3580

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x00000000…0003

0x139aab…382b

2 touches
0 conflicts

0x054c4679…2f2e

0x34b655…2a6f

2 touches
0 conflicts

0x0c1aa307…ff9c

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: 0x34b6552d…112a6f

3 conflicts on slot 0xf6476f21e7…f83580

← previous block·next block →recent activity