← previous blocknext block →recent activity

Analyzing

Block #73,336,328

12 transactions · 9 stateful · 2026-05-08 23:02:15 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,336,328  ·  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

0x8f61f264…a9ce

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x569af9e2…80ee

0x065c9d…c394

4 touches
1 conflict

0x56b770e5…4f93

0x065c9d…c394

3 touches
1 conflict

0x6a67d433…7ad7

0x065c9d…c394

3 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0xaf370227…f180

0x065c9d…c394

2 touches
0 conflicts

0xdb68ab7d…6f8f

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 0x8f61f264fe…79a9ce

← previous block·next block →recent activity