← previous blocknext block →recent activity

Analyzing

Block #73,381,561

9 transactions · 8 stateful · 2026-05-09 04:03:08 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,381,561  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x89d7c834…9479

0x065c9d…c394

4 touches
1 conflict

0xb869b869…2a5e

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x42d218f7…d32b

0x065c9d…c394

2 touches
0 conflicts

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0x67aa6dec…2eb7

0x065c9d…c394

2 touches
0 conflicts

0x71b01097…a8d9

0x065c9d…c394

2 touches
0 conflicts

0x7bd2effe…8337

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

1 conflict on slot 0x89d7c8346b…899479

← previous block·next block →recent activity