← previous blocknext block →recent activity

Analyzing

Block #73,308,268

15 transactions · 13 stateful · 2026-05-08 19:55:35 UTC

Parallelism

73/100

Blocked

23%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,308,268  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0xdc407ea3…d674

0x065c9d…c394

4 touches
1 conflict

0x945e1a29…f1ec

0x065c9d…c394

3 touches
1 conflict

0x10488e75…2cdd

0x065c9d…c394

2 touches
0 conflicts

0x32786b8e…319c

0x065c9d…c394

2 touches
0 conflicts

0x35137765…ccd2

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity