← previous blocknext block →recent activity

Analyzing

Block #73,960,623

11 transactions · 7 stateful · 2026-05-11 20:33:06 UTC

Parallelism

82/100

Blocked

14%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,960,623  ·  11 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

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x33f2d9b1…b689

0x34b655…2a6f

4 touches
1 conflict

0xf6476f21…3580

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x042f4288…4c8b

0x065c9d…c394

2 touches
0 conflicts

0x1789764f…f0c5

0x065c9d…c394

2 touches
0 conflicts

0x62cd93ce…e516

0x065c9d…c394

2 touches
0 conflicts

0xb50e6b7f…cb60

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: 0x34b6552d…112a6f

1 conflict on slot 0x0eac637818…cb36f4

← previous block·next block →recent activity