← previous blocknext block →recent activity

Analyzing

Block #73,669,133

8 transactions · 7 stateful · 2026-05-10 12:00:11 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,669,133  ·  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

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2643efd…9bdd

0x065c9d…c394

3 touches
1 conflict

0x07860638…87bd

0x065c9d…c394

3 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

2 touches
1 conflict

0x68faa0b9…14af

0x368ee5…7ca4

2 touches
0 conflicts

0x99f666e3…b2a2

0x3bd359…433a

2 touches
0 conflicts

0xfe3bddd2…8b48

0x3bd359…433a

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 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity