← previous blocknext block →recent activity

Analyzing

Block #73,374,254

12 transactions · 11 stateful · 2026-05-09 03:14:34 UTC

Parallelism

42/100

Blocked

55%

Avg conflicts / tx

1.75

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,374,254  ·  12 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

14 touches
21 conflicts

0x22e295f5…1bef

0x065c9d…c394

14 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xe57f3c88…7656

0x065c9d…c394

3 touches
1 conflict

0x4ee2d722…1c10

0x065c9d…c394

2 touches
0 conflicts

0x51e1366d…7f1d

0x065c9d…c394

2 touches
0 conflicts

0x8ee31280…a8e4

0x065c9d…c394

2 touches
0 conflicts

0xae74ee89…c58e

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

21 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity