← previous blocknext block →recent activity

Analyzing

Block #73,377,056

18 transactions · 10 stateful · 2026-05-09 03:33:12 UTC

Parallelism

78/100

Blocked

30%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,377,056  ·  18 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

0xf6c9bf9b…ac02

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xf8f1e808…a4fd

0x34b655…2a6f

4 touches
1 conflict

0x9b8800c1…ed12

0x34b655…2a6f

4 touches
1 conflict

0x1bc9b1ca…85ef

0x34b655…2a6f

4 touches
1 conflict

0xb81d3ee7…3947

0x34b655…2a6f

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

3 conflicts on slot 0xf6c9bf9b65…e4ac02

← previous block·next block →recent activity