← previous blocknext block →recent activity

Analyzing

Block #73,324,542

7 transactions · 5 stateful · 2026-05-08 21:43:56 UTC

Parallelism

71/100

Blocked

20%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,324,542  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x1c4c4567…c7f7

0x065c9d…c394

4 touches
1 conflict

0x3fdd33f2…0acd

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0x11118c62…ce19

0x065c9d…c394

2 touches
0 conflicts

0x230de0e9…b0f4

0x065c9d…c394

2 touches
0 conflicts

0x25aacc51…a819

0x065c9d…c394

2 touches
0 conflicts

0xb323303e…dbdb

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 0x1c4c4567f6…8cc7f7

← previous block·next block →recent activity