← previous blocknext block →recent activity

Analyzing

Block #73,668,715

14 transactions · 11 stateful · 2026-05-10 11:57:23 UTC

Parallelism

71/100

Blocked

27%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,668,715  ·  14 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

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x5072dd62…6e9c

0x065c9d…c394

4 touches
1 conflict

0x86f0dc7f…1fb2

0x065c9d…c394

3 touches
1 conflict

0xcdca4f89…6ee3

0x065c9d…c394

3 touches
1 conflict

0x072cbfb3…5ab4

0x065c9d…c394

3 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity