← previous blocknext block →recent activity

Analyzing

Block #73,571,714

11 transactions · 9 stateful · 2026-05-10 01:07:51 UTC

Parallelism

55/100

Blocked

56%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,571,714  ·  11 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

0x22e295f5…1bef

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xbd47d358…e86e

0x065c9d…c394

4 touches
1 conflict

0x2fddb12d…8273

0x065c9d…c394

4 touches
1 conflict

0x4703045b…322a

0x065c9d…c394

3 touches
1 conflict

0xc456f330…e929

0x065c9d…c394

3 touches
1 conflict

0x37a9c4fa…a43b

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

10 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity