← previous blocknext block →recent activity

Analyzing

Block #73,744,310

8 transactions · 8 stateful · 2026-05-10 20:27:30 UTC

Parallelism

63/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,744,310  ·  8 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

0xc3fd29b2…7773

0x065c9d…c394

4 touches
1 conflict

0xecece0aa…7e0c

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x85744637…b957

0x065c9d…c394

3 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

2 touches
0 conflicts

0x59a1cc0f…ae7c

0x065c9d…c394

2 touches
0 conflicts

0x6bad232a…32e9

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: 0x065c9d28…a9c394

1 conflict on slot 0xc3fd29b240…627773

← previous block·next block →recent activity