← previous blocknext block →recent activity

Analyzing

Block #73,598,612

37 transactions · 28 stateful · 2026-05-10 04:06:43 UTC

Parallelism

86/100

Blocked

39%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,598,612  ·  37 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8240d70c…7c3b

0x34b655…2a6f

10 touches
10 conflicts

0x219c0d71…b5fb

0xd32edf…ff58

9 touches
10 conflicts

0x42deeec2…4566

0x34b655…2a6f

6 touches
3 conflicts

0x9a8950d9…86e9

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

6 touches
3 conflicts

0x69380e29…9060

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

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

10 conflicts on slot 0x8240d70c8a…f27c3b

← previous block·next block →recent activity