← previous blocknext block →recent activity

Analyzing

Block #73,499,681

13 transactions · 12 stateful · 2026-05-09 17:09:16 UTC

Parallelism

46/100

Blocked

58%

Avg conflicts / tx

1.92

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,499,681  ·  13 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x22e295f5…1bef

0x065c9d…c394

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xa49a7f1d…56bc

0x065c9d…c394

3 touches
1 conflict

0x577be7b0…f53f

0x065c9d…c394

2 touches
0 conflicts

0xb349933d…f91b

0x065c9d…c394

2 touches
0 conflicts

0xc4959cb2…777e

0x065c9d…c394

2 touches
0 conflicts

0xae69c125…2379

0x2a68ba…90c5

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: 0x065c9d28…a9c394

21 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity