← previous blocknext block →recent activity

Analyzing

Block #74,400,726

14 transactions · 10 stateful · 2026-05-13 21:23:30 UTC

Parallelism

71/100

Blocked

30%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,400,726  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x8fa7a69c…8fd7

0x217f4e…7777

8 touches
6 conflicts

0x536e2740…61ac

0x3bd359…433a

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0002

0xa7283d…0ace

8 touches
6 conflicts

0x9fb7df68…f8a9

0xa7283d…0ace

8 touches
6 conflicts

0x9fb7df68…f8aa

0xa7283d…0ace

8 touches
6 conflicts

0x9fb7df68…f8ab

0xa7283d…0ace

8 touches
6 conflicts

0x9fb7df68…f8ac

0xa7283d…0ace

8 touches
6 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: 0x217f4e31…b57777

6 conflicts on slot 0x8fa7a69c55…388fd7

← previous block·next block →recent activity