← previous blocknext block →recent activity

Analyzing

Block #73,041,781

35 transactions · 20 stateful · 2026-05-07 14:22:35 UTC

Parallelism

89/100

Blocked

35%

Avg conflicts / tx

0.23

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,041,781  ·  35 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

0x1a4b4152…0a08

0x6ca43f…c331

6 touches
3 conflicts

0x3e4b8d9f…b8a7

0x6ca43f…c331

6 touches
3 conflicts

0x4e5ebbf7…ae70

0xc8689a…ee79

6 touches
3 conflicts

0x769b6b23…efb3

0x065c9d…c394

5 touches
3 conflicts

0x93dd61e3…ef13

0x065c9d…c394

5 touches
3 conflicts

0xfa0cf272…f3ea

0x065c9d…c394

5 touches
3 conflicts

0x5d08cf78…66f3

0x065c9d…c394

5 touches
3 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