Block #73,338,085

← previous blocknext block →recent activity

Analyzing

Block #73,338,085

20 transactions · 19 stateful · 2026-05-08 23:13:58 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

1.4

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,338,085  ·  20 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

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xd6c58560…6e55

0x065c9d…c394

3 touches
1 conflict

0x65790b38…5511

0x58e158…3d57

2 touches
0 conflicts

0x76a96399…9bbf

0x58e158…3d57

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity