← previous blocknext block →recent activity

Analyzing

Block #73,987,893

11 transactions · 11 stateful · 2026-05-11 23:35:46 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,987,893  ·  11 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0xaa3e5ab2…fd8a

0x3bd359…433a

4 touches
1 conflict

0x44ad89ba…cf83

0x7131ec…7777

4 touches
1 conflict

0xd46cd782…e7f2

0x7131ec…7777

4 touches
1 conflict

0x00000000…0000

0xc82b5c…bb3a

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0001

0xc82b5c…bb3a

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity