← previous blocknext block →recent activity

Analyzing

Block #73,261,580

17 transactions · 9 stateful · 2026-05-08 14:44:52 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.12

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,261,580  ·  17 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

0x548b5ab0…8d6c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xef9f1fe1…7ff6

0x065c9d…c394

3 touches
1 conflict

0xc9f3da1a…8a9b

0x065c9d…c394

3 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

2 touches
0 conflicts

0xda4736d0…000f

0x065c9d…c394

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

2 touches
0 conflicts

0x438cf5f6…f077

0x2a68ba…90c5

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 0x548b5ab0d8…a98d6c

← previous block·next block →recent activity