← previous blocknext block →recent activity

Analyzing

Block #73,035,137

25 transactions · 13 stateful · 2026-05-07 13:38:23 UTC

Parallelism

88/100

Blocked

23%

Avg conflicts / tx

0.16

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,035,137  ·  25 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

6 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xd574ca…7ab1

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x22c5bafc…f1fb

0x065c9d…c394

2 touches
0 conflicts

0x47d6e124…fd00

0x065c9d…c394

2 touches
0 conflicts

0x4c9f6b9a…e1a7

0x065c9d…c394

2 touches
0 conflicts

0xadbc5b90…22c4

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

← previous block·next block →recent activity