← previous blocknext block →recent activity

Analyzing

Block #73,396,189

18 transactions · 17 stateful · 2026-05-09 05:40:30 UTC

Parallelism

72/100

Blocked

29%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,396,189  ·  18 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

0x6eba5e7f…4b52

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5d70606a…1d53

0x34b655…2a6f

4 touches
1 conflict

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0xb81d3ee7…3947

0x34b655…2a6f

4 touches
1 conflict

0xfadb0d6a…e64d

0x34b655…2a6f

4 touches
1 conflict

0x273d80cd…9ecc

0x34b655…2a6f

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

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

3 conflicts on slot 0x6eba5e7f6a…ac4b52

← previous block·next block →recent activity