← previous blocknext block →recent activity

Analyzing

Block #73,706,173

20 transactions · 15 stateful · 2026-05-10 16:10:07 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,706,173  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x78ae17f2…53be

0x000000…012a

2 touches
0 conflicts

0x00000000…0001

0x010592…1c83

2 touches
0 conflicts

0x00000000…0006

0x010592…1c83

2 touches
0 conflicts

0x32d6abf2…be08

0x010592…1c83

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity