← previous blocknext block →recent activity

Analyzing

Block #73,446,649

18 transactions · 17 stateful · 2026-05-09 11:16:21 UTC

Parallelism

50/100

Blocked

59%

Avg conflicts / tx

2.17

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,446,649  ·  18 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0x23bf889b…cfaf

0x5afd3e…7620

2 touches
0 conflicts

0xe3d68b59…e36c

0x5afd3e…7620

2 touches
0 conflicts

0x00000000…0006

0x60bb42…87ea

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