← previous blocknext block →recent activity

Analyzing

Block #73,986,354

8 transactions · 6 stateful · 2026-05-11 23:25:29 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,986,354  ·  8 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbcd93426…e3c7

0x065c9d…c394

4 touches
1 conflict

0x7c41e916…8230

0x065c9d…c394

3 touches
1 conflict

0xd4497e80…82fe

0x065c9d…c394

3 touches
1 conflict

0x25fbcec0…e18c

0x065c9d…c394

2 touches
0 conflicts

0x61598ce0…1a78

0x065c9d…c394

2 touches
0 conflicts

0x6fde1380…2f7c

0x065c9d…c394

2 touches
0 conflicts

0xb556f457…7cd8

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 0x0000000000…00003d

← previous block·next block →recent activity