← previous blocknext block →recent activity

Analyzing

Block #73,578,417

12 transactions · 11 stateful · 2026-05-10 01:52:25 UTC

Parallelism

75/100

Blocked

18%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,578,417  ·  12 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xb81d3ee7…3947

0x34b655…2a6f

4 touches
1 conflict

0xb91a6f59…722c

0x34b655…2a6f

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x3817764d…242b

0x34b655…2a6f

4 touches
1 conflict

0x67f5d55a…6f4f

0x065c9d…c394

2 touches
0 conflicts

0x8df8fb36…1edc

0x065c9d…c394

2 touches
0 conflicts

0x8eefbc5e…e055

0x065c9d…c394

2 touches
0 conflicts

0xd019cc18…53bb

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 0xb81d3ee780…143947

← previous block·next block →recent activity