← previous blocknext block →recent activity

Analyzing

Block #73,798,602

10 transactions · 10 stateful · 2026-05-11 02:33:50 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,798,602  ·  10 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xf7aec201…2178

0x065c9d…c394

3 touches
1 conflict

0x1d2e3c32…75ca

0x065c9d…c394

2 touches
0 conflicts

0x21356d68…13f2

0x065c9d…c394

2 touches
0 conflicts

0x492ed5a4…366a

0x065c9d…c394

2 touches
0 conflicts

0x785d53b1…39a7

0x065c9d…c394

2 touches
0 conflicts

0xccf45220…0e5f

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 0x0000000000…00003d

← previous block·next block →recent activity