← previous blocknext block →recent activity

Analyzing

Block #73,706,455

13 transactions · 12 stateful · 2026-05-10 16:12:00 UTC

Parallelism

54/100

Blocked

50%

Avg conflicts / tx

1.46

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,706,455  ·  13 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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0x74c2e17f…d2ff

0x065c9d…c394

4 touches
1 conflict

0x0ef754e3…22cd

0x065c9d…c394

3 touches
1 conflict

0x0fd3e5ad…e10a

0x065c9d…c394

3 touches
1 conflict

0x3b2d280a…d9b2

0x065c9d…c394

3 touches
1 conflict

0x005a269c…6e9a

0x065c9d…c394

3 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: 0x065c9d28…a9c394

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity