← previous blocknext block →recent activity

Analyzing

Block #73,698,329

16 transactions · 13 stateful · 2026-05-10 15:17:11 UTC

Parallelism

56/100

Blocked

46%

Avg conflicts / tx

1.13

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,698,329  ·  16 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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x529acb6a…fcc6

0x065c9d…c394

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x022dfd4a…6567

0x34b655…2a6f

2 touches
0 conflicts

0x1528762d…c303

0x34b655…2a6f

2 touches
0 conflicts

0x5d28424b…2e40

0x34b655…2a6f

2 touches
0 conflicts

0x63fba213…5ce2

0x34b655…2a6f

2 touches
0 conflicts

0x742436a7…c4d4

0x34b655…2a6f

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 0x046a928e85…e50012

← previous block·next block →recent activity