← previous blocknext block →recent activity

Analyzing

Block #73,961,521

10 transactions · 7 stateful · 2026-05-11 20:39:04 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,961,521  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x8876d94c…8435

0x2a68ba…90c5

4 touches
1 conflict

0xa11d655c…c9a0

0xd32edf…ff58

3 touches
1 conflict

0x60923795…a7da

0xa6afd3…d132

3 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0xa3fbb70a…69af

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e017

0x188d58…ea8e

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

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

1 conflict on slot 0x8876d94c2a…cc8435

← previous block·next block →recent activity