← previous blocknext block →recent activity

Analyzing

Block #73,660,446

17 transactions · 10 stateful · 2026-05-10 11:01:30 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,660,446  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x6aa0281c…adb5

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xf8480e2a…dff2

0x1b6862…e19c

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0009

0x04ddf6…7f33

2 touches
0 conflicts

0xaeabffea…5dd4

0x0a3323…0a3c

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 0x6aa0281cb6…35adb5

← previous block·next block →recent activity