← previous blocknext block →recent activity

Analyzing

Block #73,386,923

8 transactions · 7 stateful · 2026-05-09 04:38:50 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.63

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,386,923  ·  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

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x339a7815…5021

0x065c9d…c394

3 touches
1 conflict

0x868a746b…b9a2

0x065c9d…c394

3 touches
1 conflict

0x4c1a6d51…e836

0x065c9d…c394

2 touches
0 conflicts

0x6daa0d4c…702b

0x065c9d…c394

2 touches
0 conflicts

0x8d581536…0dfb

0x065c9d…c394

2 touches
0 conflicts

0xbf8825a8…b7c5

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

3 conflicts on slot 0x4d87512b00…43897c

← previous block·next block →recent activity