← previous blocknext block →recent activity

Analyzing

Block #73,324,284

17 transactions · 16 stateful · 2026-05-08 21:42:13 UTC

Parallelism

65/100

Blocked

38%

Avg conflicts / tx

1.41

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,324,284  ·  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

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x43f7c27e…0399

0x065c9d…c394

4 touches
2 conflicts

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x6a2375c9…0146

0x065c9d…c394

3 touches
1 conflict

0x6f8f258f…6330

0x065c9d…c394

3 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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity