← previous blocknext block →recent activity

Analyzing

Block #73,989,731

6 transactions · 5 stateful · 2026-05-11 23:48:12 UTC

Parallelism

50/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,989,731  ·  6 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xa3feb7ad…94f1

0x065c9d…c394

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x7b2d2581…17c6

0x065c9d…c394

3 touches
1 conflict

0x9643a575…df2e

0x065c9d…c394

3 touches
1 conflict

0x2c4780c3…6d46

0x065c9d…c394

2 touches
0 conflicts

0x4ef166ad…196e

0x065c9d…c394

2 touches
0 conflicts

0x6b46715d…83bc

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