← previous blocknext block →recent activity

Analyzing

Block #73,693,626

13 transactions · 13 stateful · 2026-05-10 14:45:29 UTC

Parallelism

46/100

Blocked

46%

Avg conflicts / tx

1.46

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,693,626  ·  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

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x3e27a3f2…87ba

0x065c9d…c394

2 touches
0 conflicts

0xa06edb22…2d4f

0x065c9d…c394

2 touches
0 conflicts

0xb77c5b09…a7f0

0x065c9d…c394

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity