← previous blocknext block →recent activity

Analyzing

Block #73,493,276

32 transactions · 26 stateful · 2026-05-09 16:26:39 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,493,276  ·  32 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc89c9c54…7ad6

0xd32edf…ff58

9 touches
10 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x1c354dc0…96de

0x754704…b603

6 touches
3 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

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

10 conflicts on slot 0xc89c9c5408…1d7ad6

← previous block·next block →recent activity