← previous blocknext block →recent activity

Analyzing

Block #73,651,190

16 transactions · 14 stateful · 2026-05-10 09:59:10 UTC

Parallelism

75/100

Blocked

57%

Avg conflicts / tx

0.94

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,651,190  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x7f81fb82…633e

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x15d039e7…4bb6

0x34b655…2a6f

6 touches
3 conflicts

0x56bf2a47…527f

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2ff023b…40ae

0x065c9d…c394

2 touches
0 conflicts

0xf637e363…8c71

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

6 conflicts on slot 0x7f81fb82c1…ec633e

← previous block·next block →recent activity