← previous blocknext block →recent activity

Analyzing

Block #73,986,969

17 transactions · 17 stateful · 2026-05-11 23:29:34 UTC

Parallelism

65/100

Blocked

59%

Avg conflicts / tx

1.41

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,986,969  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x6f08361d…bda6

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x08d73a61…529e

0x065c9d…c394

4 touches
1 conflict

0x2e2214a9…fe0d

0x5d823e…89c6

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x5d823e…89c6

4 touches
1 conflict

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 0x6f08361da9…89bda6

← previous block·next block →recent activity