← previous blocknext block →recent activity

Analyzing

Block #73,984,025

17 transactions · 17 stateful · 2026-05-11 23:09:49 UTC

Parallelism

71/100

Blocked

29%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,984,025  ·  17 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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x44ad89ba…cf83

0x7131ec…7777

4 touches
1 conflict

0xd46cd782…e7f2

0x7131ec…7777

4 touches
1 conflict

0x00000000…0000

0xc82b5c…bb3a

4 touches
1 conflict

0x00000000…0001

0xc82b5c…bb3a

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity