← previous blocknext block →recent activity

Analyzing

Block #73,663,981

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

Parallelism

69/100

Blocked

31%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

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

0xb5064564…3ee1

0xd32edf…ff58

7 touches
6 conflicts

0x1c5a3264…4d4f

0x065c9d…c394

6 touches
3 conflicts

0xae69c125…2379

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c3

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0005

0x5e60bc…fe22

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: 0xd32edf66…9fff58

6 conflicts on slot 0xb5064564b0…753ee1

← previous block·next block →recent activity