Block #73,324,364

← previous blocknext block →recent activity

Analyzing

Block #73,324,364

12 transactions · 9 stateful · 2026-05-08 21:42:45 UTC

Parallelism

83/100

Blocked

22%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,324,364  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x711e6f55…aa8d

0x34b655…2a6f

4 touches
1 conflict

0xac206e47…ef7d

0x34b655…2a6f

4 touches
1 conflict

0x813682bb…30c7

0x065c9d…c394

2 touches
0 conflicts

0x83c1906a…29f8

0x065c9d…c394

2 touches
0 conflicts

0xa90bf350…379f

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 0x0b390c6160…02dc07

← previous block·next block →recent activity